development/github-desktop
development/github-desktop
1
0
Fork 0
mirror of https://github.com/desktop/desktop synced 2024-07-17 02:57:57 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
github-desktop/docs/integrations/azure-devops.md
Matt Busche 4cf7f414b3
Update directions due to website change (#1)
2020-08-17 13:40:38 -05:00

2.1 KiB
Raw Blame History

Authenticating to Azure DevOps with GitHub Desktop

Creating a Personal Access Token in Azure DevOps

To authenticate against Azure DevOps repositories you will need to create a personal access token.

  1. Go to your Azure DevOps account and select Personal Access Tokens in the user settings dropdown:

  1. Click New token to create a new personal access token. Give it a name, select the organizations you would like the token to apply to, and choose when you would like the token to expire.

    • Note: For the Expiration dropdown you can select Custom defined to select an expiration date up to a year in advance of the current date. This is useful if you do not want to have to periodically go back and generate a new token after your current token expires.

3 . Under the Scopes section choose Custom defined and then select Read & Write under the Code section. This will grant GitHub Desktop read and write access to your Azure DevOps repositories.

4 . Click Create to create a new token, and then copy it to your clipboard.

Cloning your Azure DevOps repository in GitHub Desktop

  1. Open GitHub Desktop and go to File > Clone Repository > URL. Enter the Git URL of your Azure DevOps repository. Make sure you enter the correct URL, which should have the following structure:

    https://<username>@dev.azure.com/<username>/<project_name>/_git/<repository_name>

  2. You will receive an Authentication Failed error. Enter your Azure DevOps username and paste in the token you just copied to your clipboard. Click Save and Retry to successfully clone the repository to your local machine in GitHub Desktop.

  • Note: Your Azure DevOps credentials will be securely stored on your local machine so you will not need to repeat this process when cloning another repository from Azure DevOps.