Previously you needed to manually generate a token but now you can automatically get the access token and life is way easier because of it. The Team Services extension in VS Code needs you to authenticate with VSTS with a Personal access token (PAT). You should get a message from the Team Services Extension that you are not logged-in to Team Services, let’s rectify that. This all becomes active when you load a folder that is a Git repository. It also shows you what has changed and is yet to be committed. The third tab is your Git tab, allowing you the ability to commit, pull, and sync your repos. This will populate the explorer with the structure of the repo. Select and open the folder of the repo we just cloned. In VS Code, click on the Explorer tab (the top one - looks like some files) and then click Open Folder. Nice work! This has put in a folder of the same name as your repo in the folder you ran the clone. Then run git clone You may be asked to authenticate with Team Services, but after you should see something like this… Now open a command prompt and navigate to the folder you would like to put your cloned repo. If you look to the right of the Files you will come across a Clone button, click it and copy the Clone URL. You should see something like below, which is my simple Git repository, complete with just a readme file. In Visual Studio Team Services, navigate to the Code > Files section of your project. The Team Services extension for VS Code.Whilst at Ignite I mentioned this to one of the VSTS team and was hit with a very passionate response saying that we should take the time to try it out. This is for a few reasons, but one of the big ones is the rich functionality that is provided in Visual Studio Code. All of my day-to-day projects are using Team Foundation Version Control (TFVC) repositories, but recently we have been considering using Git.

Connect visual studio code to github