When you identify the local repository the Visual Studio Team Services module will take over. The process is straight forward – install the extensions and locate the local repository. Once you have Visual Studio Code set up you can delete the Personal Access token as the module in Visual Studio Code does a better job with authentication. The temporary work around is to use a Personal Access token. As a result when I first set up a clone from my work machine I am redirected to use my work sign-in which promptly fails. I get that a lot as I have a personal Visual Studio account that shares its primary email address with my work account. When cloning or fetching the repository you might encounter an error where you need to sign into Visual Studio Services but for one reason or another your credentials are not accepted. If this process fails then it is likely that you have authentication challenges. Tap on the Fetch origin button and after a brief period where the arrows spin the status should change to ‘Last fetched…’: You might notice that the ‘Fetch origin’ state is ‘Never fetched’. You can validate that the set-up is complete by viewing the ‘History’ tab in GitHub Desktop and performing a ‘Fetch’: Remember the cloning process will not work if a folder of the same name is already present. This might look good in the browser but in reality those spaces are ’s and they (a) make the folder path longer (b) look amateurish. In the earlier Visual Studio Services image you can see that I used spaces when creating the project. You can replace it with something shorter or meaningful. You do not need to use the repository name. The other aspect is that the cloning process will want to add the repository as a new folder which uses the repository name. If you do use OneDrive you will get file conflict errors when Git attempts to synchronise the local and source repositories.In the image above, all of my repositories are stored as sub-folders in Documents\GitHub. If this is the first time that you are using Git then I recommend that you manually create a new folder for all of your work somewhere on your local drive (you can do this with File Explorer – no special tools required). You can then use the URL to clone the repository: You can then grab the URL from the browser address bar. The URL is displayed when you first create a project but thereafter it is not that obvious to find… The easiest way is to go to the ‘Code’ section in Visual Studio Services and then select the relevant project from the ‘Files’ tab. One thing that Visual Studio Services does not make easy is to get the URL for your repository. I recommend that you cancel the pop-up and select ‘Clone a repository’ from the main screen: When you install GitHub Desktop it will want you to create a repository when it starts up. In following the post I learned several lessons that I thought I’d share. The end result is that your scripts can be stored in a secure source repository. In the post Jethro walks through the process of setting up Visual Studio Code to work with Visual Studio Services. Recently I came across an excellent blog post from Jethro Seghers that covered getting started with Office 365 PowerShell Automation.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |