mirror of
https://github.com/desktop/desktop
synced 2024-09-29 21:03:35 +00:00
Compare commits
5 commits
d2c6ddb164
...
7ca7c26111
Author | SHA1 | Date | |
---|---|---|---|
7ca7c26111 | |||
d32900c3a2 | |||
376f9b642d | |||
ffc600a12d | |||
df4b2d35f3 |
BIN
docs/assets/ado-prompt.png
Normal file
BIN
docs/assets/ado-prompt.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 41 KiB |
BIN
docs/assets/bitbucket-prompt.png
Normal file
BIN
docs/assets/bitbucket-prompt.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 47 KiB |
BIN
docs/assets/git-credential-manager.png
Normal file
BIN
docs/assets/git-credential-manager.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 65 KiB |
BIN
docs/assets/gitlab-prompt.png
Normal file
BIN
docs/assets/gitlab-prompt.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 42 KiB |
|
@ -1,5 +1,19 @@
|
|||
# Authenticating to Azure DevOps with GitHub Desktop
|
||||
|
||||
GitHub Desktop now provides support for [Git Credential Manager (GCM)](https://gh.io/gcm), which makes the task of authenticating to Azure DevOps repositories easy and secure. This feature can be enabled by going to **File** > **Options** > **Advanced** on Windows, or **GitHub Desktop** > **Preferences** > **Advanced** on macOS, and then selecting the **Use Git Credential Manager** checkbox.
|
||||
|
||||
![screenshot of the GitHub Desktop settings menu with the "Use Git Credential Manager" checkbox outlined](/docs/assets/git-credential-manager.png)
|
||||
|
||||
When GCM is enabled all credentials for Azure DevOps will be handled, and stored, outside of GitHub Desktop. GCM supports browser authentication and will avoid the need to create personal access tokens (PATs).
|
||||
|
||||
Your browser will open to authenticate to your Azure DevOps account using GCM when you go to **File** > **Clone Repository** > **URL** and enter the HTTPS clone URL of the repository.
|
||||
|
||||
![screenshot of a browser window showing the option to pick a Microsoft account](/docs/assets/ado-prompt.png)
|
||||
|
||||
If you would prefer not to use GCM and need to create a personal access token in Azure DevOps you can follow the steps below.
|
||||
|
||||
|
||||
|
||||
## Creating a Personal Access Token in Azure DevOps
|
||||
|
||||
To authenticate against Azure DevOps repositories you will need to create a personal access token.
|
||||
|
|
|
@ -1,5 +1,17 @@
|
|||
# Authenticating to Bitbucket with GitHub Desktop
|
||||
|
||||
GitHub Desktop now provides support for [Git Credential Manager (GCM)](https://gh.io/gcm), which makes the task of authenticating to Bitbucket repositories easy and secure. This feature can be enabled by going to **File** > **Options** > **Advanced** on Windows, or **GitHub Desktop** > **Preferences** > **Advanced** on macOS, and then selecting the **Use Git Credential Manager** checkbox.
|
||||
|
||||
![screenshot of the GitHub Desktop settings menu with the "Use Git Credential Manager" checkbox outlined](/docs/assets/git-credential-manager.png)
|
||||
|
||||
When Git Credential Manager is enabled all credentials for Bitbucket will be handled, and stored, outside of GitHub Desktop. Git Credential Manager supports browser authentication and will avoid the need to create personal access tokens (PATs).
|
||||
|
||||
The prompt to authenticate to your Bitbucket account using GCM will be shown when you go to **File** > **Clone Repository** > **URL** and enter the HTTPS clone URL of the repository.
|
||||
|
||||
![screenshot of a prompt showing the option to sign in with your browser to an Atlassian account](/docs/assets/bitbucket-prompt.png)
|
||||
|
||||
If you would prefer not to use GCM and need to create a personal access token in Bitbucket you can follow the steps below.
|
||||
|
||||
## Creating a Personal Access Token in Bitbucket
|
||||
|
||||
To authenticate against Bitbucket repositories you will need to create a personal access token.
|
||||
|
|
|
@ -1,5 +1,17 @@
|
|||
# Authenticating to GitLab with GitHub Desktop
|
||||
|
||||
GitHub Desktop now provides support for [Git Credential Manager (GCM)](https://gh.io/gcm), which makes the task of authenticating to GitLab repositories easy and secure. This feature can be enabled by going to **File** > **Options** > **Advanced** on Windows, or **GitHub Desktop** > **Preferences** > **Advanced** on macOS, and then selecting the **Use Git Credential Manager** checkbox.
|
||||
|
||||
![screenshot of the GitHub Desktop settings menu with the "Use Git Credential Manager" checkbox outlined](/docs/assets/git-credential-manager.png)
|
||||
|
||||
When GCM is enabled all credentials for GitLab will be handled, and stored, outside of GitHub Desktop. GCM supports browser authentication and will avoid the need to create personal access tokens (PATs).
|
||||
|
||||
The prompt to authenticate to your GitLab account using GCM will be shown after you enter the HTTPS clone URL of the GitLab repository by going to **File** > **Clone Repository** > **URL**.
|
||||
|
||||
![screenshot of a prompt showing the option to sign in with your browser to a GitLab account](/docs/assets/gitlab-prompt.png)
|
||||
|
||||
If you would prefer not to use GCM and need to create a personal access token in GitLab you can follow the steps below.
|
||||
|
||||
## Creating a Personal Access Token in GitLab
|
||||
|
||||
To authenticate against GitLab repositories you will need to create a personal access token.
|
||||
|
|
Loading…
Reference in a new issue