Menu
To configure Git settings in Visual Studio, choose Settings from the top-level Git menu. Choose Git Global Settings or Git Repository Settings to view and configure global-level or repository-level settings. You can configure several common Git settings, as described in the following sections of this article.
Git Credential Manager creates and stores credentials to access Git repositories on a host of platforms. We hold in the highest regard the need to keep your credentials and access secure. That's why we always keep your credentials stored using industry standard encryption and storage APIs.
You need to enable Alternate Authentication Credentials if you want to use other Git clients outside of Visual Studio...
To set up alternate creds in Visual Studio Team Services (VSTS), click on your name/icon on the top right -> Security -> Alternate Authentication Credentials
Edit: Add more details about this from VSTS (taken from the alternate credentials screen)...
ALTERNATE AUTHENTICATION CREDENTIALS
Some applications that work outside the browser (including Team Explorer Everywhere command line client and the git-tf utility) require basic authentication credentials. Other applications do not properly handle using an e-mail address for the user name during authentication.
To work with these applications, you need to enable alternate credentials, set a password, and optionally set a secondary user name not in the form of an e-mail address. Please note that alternate credentials cannot be used to sign in to the service from a web browser or outside of these applications.
Enable alternate authentication credentials and set secondary username
Create a personal access token for your Visual Studio Team Services account and copy the token
Open Git Bash and go to the folder that you cloned your repository to and enter the following command to make sure it stores the credentials and you don't need to enter it every time:
git config credential.helper store
git pull origin [your branch]
It asks for user name and password. Enter user name and token as password
On Windows, you can easily create a Personal Access Token using the Git Credential Manager. It's what Visual Studio Team Services now seems to recommend over the Alternate authentication credentials.
Just install that utility, and then the next time you git pull from Git Bash, it will prompt you for your Visual Studio Team Services access credentials. It will then create a Personal Access Token in your VSTS account, and add a couple of entries to your local Windows Credentials store.
Quote from the site:
It magically works when credentials are needed. For example, when pushing to Visual Studio Team Services, it automatically opens a window and initializes an oauth2 flow to get your token.
I noticed the wording (and location) of the menus changed in Visual Studio Team Services. It is now located in the drop-down menu at the top-right corner (with your initials or photo) Security → Alternate authentication credentials. Just enable and make up your username and password.
When using Atlassian SourceTree you need the basic credentials setup in Visual Studio Team Services (VSTS) like in the accepted answer.
Then in SourceTree go to menu Tools → Options → Authentication tab.
You need to set the non-email username that you set up as basic username credentials for the XXX.visualstudio.com host.
You will then be prompted for the password when accessing that VSTS Git repository.
Downloading the latest version of Git and including the Git Credential Manager worked for me.
Use Git Credential Managers to Authenticate to VSTS
As per 2017-06-21, the page to enable alternate authentication settings is at
the link https://*YOUR_USER_NAME*.visualstudio.com/_details/security/altcreds.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With