>>Perhaps I used the wrong interface, I went on the Cloud interface and then I have to use the command line to stage and push the files.
>
>We are using a local environment. But, I believe this goes in the same way.
>
>As far as the tutorials go, I have went through some of them. But, all that targets as those who want to do repetitive tasks. As for me, I do not have time to do repetitive things over and over again. So, basically, I automated everything and the tutorials only served to give me a head start.
>
>Note also that GIT offers support to integrate itself over certain environments such as .NET. You probably does not have support for VFP. But, that does not change anything. In Visual Studio, it plugged itself into the environment and I didn't really want to have it in there. So, I went into the settings and disable those plugins.
>
>Here is a set of commands I use to push things from local to server. This assumes I have an interface where I have a Status button. When I click on it, it gives me all files which have been changed (new ones, updated ones and deleted ones). I simply cut & paste that into the Files field. Then, I enter my JIRA item(s) related to the deployment in another field. Then, in the Tag(s) field, I enter v2.1, for example, which follows where I am in the BitBucket last deployment version value. The code you see here uses some framework classes to do a few things. But, that should give you an idea at how you can automate things up to BitBucket.
>
>Code for the Status button:
>

>...

>
>The code is in .NET but that is fairly easy to understand.
>
>I also attached an image of my interface.

Thanks a lot, this will get me into the right direction.