Use of Bitbucket for source control
Posted: Mon Jul 23, 2018 3:19 pm
I have applied for using Bitbucket for source control. I have a few questions especially for others using Bitbucket already.
First, I wondered why small teams (max 5 users) would pay Microsoft for private gits when you can get this for free from an Australian company not being Microsoft?
Second I am confused especially by one thing. When I create a repository in the Bitbucket cloud (website), as administrator, I can clone it to my local Pc using Sourcetree for it which asks a directory, e.g. e:BitBucketsomething. But after that I can't commit from Visual Studio; the option is not there. For that I first have to choose File/Add to source control. This creates a directory .git en 2 files .gitattributes en .gitignore within my project directory. If I would delete those, source control is gone.
But I want to commit changes to the local (cloned) copy of my Bitbucket repository, which resides on another disk (e:BitBucketsomething). Now I have two local repo's and I don't want the one created in my project directory.
Only alternative is using their program Sourcetree which simply watches directory content change and you can commit and pull/push from there, which I in this case rather do from Visual Studio.
How do I accomplish this?
Dick
First, I wondered why small teams (max 5 users) would pay Microsoft for private gits when you can get this for free from an Australian company not being Microsoft?
Second I am confused especially by one thing. When I create a repository in the Bitbucket cloud (website), as administrator, I can clone it to my local Pc using Sourcetree for it which asks a directory, e.g. e:BitBucketsomething. But after that I can't commit from Visual Studio; the option is not there. For that I first have to choose File/Add to source control. This creates a directory .git en 2 files .gitattributes en .gitignore within my project directory. If I would delete those, source control is gone.
But I want to commit changes to the local (cloned) copy of my Bitbucket repository, which resides on another disk (e:BitBucketsomething). Now I have two local repo's and I don't want the one created in my project directory.
Only alternative is using their program Sourcetree which simply watches directory content change and you can commit and pull/push from there, which I in this case rather do from Visual Studio.
How do I accomplish this?
Dick