Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/notify-non-employee-comments.yml
Original file line number Diff line number Diff line change
Expand Up @@ -249,7 +249,7 @@ jobs:
type: 'section',
text: {
type: 'mrkdwn',
text: `*${title}*\nComment and review bodies omitted. Follow the links to read them on GitHub.` +
text: `*${title}*\nCovers the 24 hours up to the most recent 16:20 UTC.` +
(shortened ? '\n_Digest shortened to fit one Slack table. Some authors or links are omitted._' : ''),
},
},
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,27 @@ If you see the error `The file provided is not a valid GitHub Enterprise Server

{% data variables.product.company_short %} strongly recommends regular backups of your instance's configuration and data. Before you proceed with any upgrade, back up your instance, then validate the backup in a staging environment. For more information, see [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance) and [AUTOTITLE](/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).

{% ifversion saml-nameid-case-sensitive-upgrade %}

## SAML NameID matching is case-sensitive

This change applies to {% data variables.product.prodname_ghe_server %} **3.19.16, 3.20.12, 3.21.10, and 3.22.5**, released on November 17, 2026. It does not apply to {% data variables.product.prodname_ghe_cloud %} or to {% data variables.product.prodname_ghe_server %} instances with SCIM provisioning enabled.

A security fix changes how SAML `NameID` values are matched to existing accounts. Differences in capitalization, accents, or trailing spaces are rejected rather than ignored. This helps prevent a SAML sign-in from selecting the wrong {% data variables.product.github %} account.

If the `NameID` sent by your identity provider (IdP) during SAML authentication does not exactly match the user's stored SAML mapping on {% data variables.product.prodname_ghe_server %}, authentication fails. For example, an incoming `NameID` of `Mona` no longer matches a stored `NameID` of `mona`. The user sees the error `Another user already owns the account. Please have your administrator check the authentication log.`

Before upgrading, verify that the SAML `NameID` values sent by your IdP match the stored SAML mapping `NameID` values exactly, including the same uppercase and lowercase letters.

1. Check the user's stored SAML `NameID` on the **Security** tab in the site admin dashboard. For more information, see [AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/updating-a-users-saml-nameid). You can also export mappings using `ghe-saml-mapping-csv --dump`. This utility does not support instances using SCIM provisioning.
1. Check the incoming SAML `NameID` for the user. Temporarily enable SAML debugging, reproduce the user's SAML sign-in attempt, and inspect the SAML response's `NameID` in the `systemd` journal logs for `github-unicorn`. Disable debugging immediately afterward to avoid excessive logging and potential performance impact. For more information, see [AUTOTITLE](/admin/managing-iam/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging).

If the values differ, update the user's stored SAML `NameID` mapping to match the value sent by your IdP.

We are working to restore the previous case-insensitive SAML `NameID` matching behavior. The release notes will announce when this update is available.

{% endif %}

## Lifting the pause on upgrades to version 3.15 and above

We have lifted the pause on upgrades to versions 3.15, 3.16, and 3.17. You can now upgrade to 3.15.12, 3.16.8, 3.17.5, or later. We do not recommend upgrading to earlier releases of 3.15, 3.16, or 3.17. As an additional step, it is recommended to check system capacity before upgrading. See [AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/check-system-capacity-before-upgrading).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,8 @@ category:
{% data reusables.git.remove-git-remote %}
1. [Add the repository to GitHub Desktop](/desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop).
{% data reusables.desktop.publish-repository %}
1. In the "Publish Repository" window, in the "Name" field, type the desired name of the repository or use the default current local repository name.
1. In the "Publish Repository" window, select the **Account** dropdown menu, then click the account you want to publish the repository with. If the repository is assigned to an account that's signed in, that account is selected. For more information, see [AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/using-multiple-accounts-in-github-desktop).
1. In the "Name" field, type the desired name of the repository or use the default current local repository name.
1. Optionally, add a description for the repository.
1. Optionally, to publish a public repository, deselect **Keep this code private**.
1. Select the "Organization" dropdown menu, then either click the organization where you want to publish the repository, or, to publish the repository to your personal account, click **None**.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,8 @@ When you use {% data variables.product.prodname_desktop %} to push a change to a

You can also clone a repository directly from {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}. For more information, see [AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop).

If you're signed in to more than one account, {% data variables.product.prodname_desktop %} assigns each cloned repository to one of your accounts. For more information, see [AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/using-multiple-accounts-in-github-desktop).

## Cloning a repository

{% data reusables.desktop.choose-clone-repository %}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ To keep your account secure, you must authenticate before you can use {% data va

Before you authenticate, {% data reusables.desktop.get-an-account %}

You can sign in to more than one account on the same host, such as a personal account and a work account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see [AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/using-multiple-accounts-in-github-desktop).

{% mac %}

## Authenticating to your {% data variables.product.github %} account
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ children:
- /setting-up-github-desktop
- /installing-github-desktop
- /authenticating-to-github-in-github-desktop
- /using-multiple-accounts-in-github-desktop
- /about-connections-to-github-in-github-desktop
- /updating-github-desktop
- /uninstalling-github-desktop
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,188 @@
---
title: Using multiple accounts in GitHub Desktop
shortTitle: Multiple accounts
intro: Sign in to more than one account on the same host, and choose which account {% data variables.product.prodname_desktop %} uses for each repository.
versions:
fpt: '*'
ghec: '*'
ghes: '*'
category:
- Set up GitHub Desktop
---

## About multiple accounts

You can sign in to {% data variables.product.prodname_desktop %} with more than one account on the same host. For example, you can use a personal account and a work account on {% data variables.product.prodname_dotcom_the_website %}, or several accounts on {% data variables.product.prodname_ghe_server %} or {% data variables.enterprise.data_residency_site %}. You don't need to sign out of one account to use another.

A repository in {% data variables.product.prodname_desktop %} can be assigned to one account on the repository's host. {% data variables.product.prodname_desktop %} uses the assigned account for {% data variables.product.github %} API requests and for HTTPS authentication when Git pushes, pulls, or fetches.

{% data variables.product.prodname_copilot_short %} features in {% data variables.product.prodname_desktop %}, such as generating commit messages, use the repository's account if it has access to {% data variables.product.prodname_copilot_short %}. Otherwise, they use another signed-in account that does.

If you used {% data variables.product.prodname_desktop %} before multiple accounts were supported, each of your existing repositories is assigned to the account you were signed in to on that host. If you only use one account, nothing changes.

> [!NOTE]
> The account assigned to a repository doesn't change the name and email address that Git uses as the author of your commits. For more information, see [AUTOTITLE](/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop).
## Adding another account

{% mac %}

{% data reusables.desktop.mac-select-desktop-menu %}

1. In the "Settings" window, on the **Accounts** pane, click **Add {% data variables.product.prodname_dotcom_the_website %} account**. To sign in to {% data variables.product.prodname_ghe_server %} or {% data variables.enterprise.data_residency_site %}, click **Add {% data variables.product.prodname_enterprise %} account** instead.

![Screenshot of the "Accounts" pane in "Settings" on a Mac. Two {% data variables.product.prodname_dotcom_the_website %} accounts are listed. "Add {% data variables.product.prodname_dotcom_the_website %} account" is outlined in dark orange.](/assets/images/help/desktop/mac-accounts-multiple-accounts.png)

1. Follow the prompts to sign in. See [AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop).

> [!TIP]
> Your browser might ask which {% data variables.product.github %} account to use, even if you're already signed in. Choose the account you want to add, or sign in to a different account.
{% endmac %}

{% windows %}

{% data reusables.desktop.windows-choose-options %}

1. In the "Options" window, on the **Accounts** pane, click **Add {% data variables.product.prodname_dotcom_the_website %} account**. To sign in to {% data variables.product.prodname_ghe_server %} or {% data variables.enterprise.data_residency_site %}, click **Add {% data variables.product.prodname_enterprise %} account** instead.

![Screenshot of the "Accounts" pane in "Options" on Windows. Two {% data variables.product.prodname_dotcom_the_website %} accounts are listed. "Add {% data variables.product.prodname_dotcom_the_website %} account" is outlined in dark orange.](/assets/images/help/desktop/windows-accounts-multiple-accounts.png)

1. Follow the prompts to sign in. For more information, see [AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop).

> [!TIP]
> Your browser might ask which {% data variables.product.github %} account to use, even if you're already signed in. Choose the account you want to add, or sign in to a different account.
{% endwindows %}

The "Accounts" pane lists your {% data variables.product.prodname_dotcom_the_website %} accounts under "{% data variables.product.prodname_dotcom_the_website %}". Your {% data variables.product.prodname_ghe_server %} and {% data variables.enterprise.data_residency_site %} accounts are listed under "{% data variables.product.prodname_enterprise %}", grouped by hostname.

## How {% data variables.product.prodname_desktop %} chooses an account for a repository

{% data variables.product.prodname_desktop %} assigns an account to a repository when you clone, add, or publish it.

* **Cloning from the "{% data variables.product.github %}" tab:** Choose an account from the **Account** dropdown menu at the top of the "Clone a Repository" window. This dropdown menu only appears if you're signed in to more than one account. The list shows the repositories that account can access. When you clone, the repository is assigned to that account. For more information, see [AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop).
* **Cloning from the "URL" tab, or adding a local repository:** {% data variables.product.prodname_desktop %} checks which of your accounts on the repository's host can access the repository.
* If one account can access it, the repository is assigned to that account.
* If more than one account can access it, {% data variables.product.prodname_desktop %} asks you to choose. Every account can access a public repository, so you're always asked to choose if you're signed in to more than one account on its host.
* If none of your accounts can access it, the repository is added without an assigned account. If you're cloning a private repository over HTTPS, the clone fails.
* **Publishing a repository:** Choose an account from the **Account** dropdown menu in the "Publish Repository" window. If the repository's assigned account is signed in, that account is selected. For more information, see [AUTOTITLE](/desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop).

### Choosing an account when {% data variables.product.prodname_desktop %} asks

If a repository doesn't have an assigned account, the "Repository account" window opens when {% data variables.product.prodname_desktop %} needs one. For example:

* Git needs HTTPS credentials to push or pull.
* {% data variables.product.prodname_desktop %} refreshes pull requests or creates a fork.

Background fetches never open this window. If you aren't signed in to any account on the repository's host, {% data variables.product.prodname_desktop %} asks you to sign in instead.

If the repository's assigned account is signed out, the "Repository account" window asks you to sign in to that account. Click **Sign in** to sign in again. If you're signed in to another account on the same host, you can click **Choose another account** to assign that account to the repository instead.

To choose an account for a repository that doesn't have one:

1. In the "Repository account" window, select the **Account** dropdown menu, then click the account you want to use for this repository. The list only shows accounts on the repository's host.

If the account you want isn't listed, click **Cancel**, sign in to the account, then try again. For more information, see [Adding another account](#adding-another-account).

{% mac %}

![Screenshot of the "Repository account" window on a Mac. It asks which account to use for Spoon-Knife on {% data variables.product.prodname_dotcom_the_website %}, with an "Account" dropdown.](/assets/images/help/desktop/mac-repository-account-dialog.png)

{% endmac %}

{% windows %}

![Screenshot of the "Repository account" window on Windows. It asks which account to use for Spoon-Knife on {% data variables.product.prodname_dotcom_the_website %}, with an "Account" dropdown.](/assets/images/help/desktop/windows-repository-account-dialog.png)

{% endwindows %}

1. Click **Use account**.

## Changing the account for a repository

You can change the account for any repository that has a remote on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_ghe_server %}, or {% data variables.enterprise.data_residency_site %}. You can only choose accounts that are signed in to the repository's host.

### Using repository settings

{% data reusables.desktop.open-repository-settings %}
1. In the "Repository Settings" window, on the **Remote** pane, select the **Account** dropdown menu, then click the account you want to use.

To remove the repository's account, click **None (unassigned)**.

{% mac %}

![Screenshot of the "Remote" pane in the "Repository Settings" window on a Mac. The "Account" dropdown is outlined in dark orange.](/assets/images/help/desktop/mac-repository-settings-account.png)

{% endmac %}

{% windows %}

![Screenshot of the "Remote" pane in the "Repository settings" window on Windows. The "Account" dropdown is outlined in dark orange.](/assets/images/help/desktop/windows-repository-settings-account.png)

{% endwindows %}

1. Click **Save**.

### Using the repository list

If a repository has a remote on a {% data variables.product.github %} host and there's more than one account to choose from, you can switch the repository's account from the repository list.

1. In the repository bar, click **Current Repository**.
1. Right-click the repository, select **Account**, then click the account you want to use.

The current account has a checkmark. If the current account is signed out, it's listed as "@USERNAME (Signed out)".

{% mac %}

![Screenshot of a repository's context menu in the repository list on a Mac. The "Account" submenu is open and shows two accounts.](/assets/images/help/desktop/mac-repository-list-account-submenu.png)

{% endmac %}

{% windows %}

![Screenshot of a repository's context menu in the repository list on Windows. The "Account" submenu is open and shows two accounts.](/assets/images/help/desktop/windows-repository-list-account-submenu.png)

{% endwindows %}

You can also open a repository's settings from the same context menu. Right-click the repository, then click **Repository Settings…**.

## Signing out of an account

When you sign out of an account that has repositories assigned to it, {% data variables.product.prodname_desktop %} asks whether to keep those assignments.

{% mac %}

{% data reusables.desktop.mac-select-desktop-menu %}

1. In the "Settings" window, on the **Accounts** pane, next to the account you want to sign out of, click **Sign Out**.
1. If repositories are assigned to the account, choose what happens to them in the "Sign out of @USERNAME?" window.
* To keep the assignments, leave **Clear repository account assignments** deselected. When you sign in to the account again, {% data variables.product.prodname_desktop %} uses it for these repositories again.
* To remove the assignments, select **Clear repository account assignments**. {% data variables.product.prodname_desktop %} asks you to choose an account the next time it needs credentials for these repositories.

![Screenshot of the "Sign out of @octocat?" window on a Mac, with a "Clear repository account assignments" checkbox.](/assets/images/help/desktop/mac-sign-out-account-dialog.png)

1. Click **Sign out**.

{% endmac %}

{% windows %}

{% data reusables.desktop.windows-choose-options %}

1. In the "Options" window, on the **Accounts** pane, next to the account you want to sign out of, click **Sign out**.
1. If repositories are assigned to the account, choose what happens to them in the "Sign out of @USERNAME?" window.
* To keep the assignments, leave **Clear repository account assignments** deselected. When you sign in to the account again, {% data variables.product.prodname_desktop %} uses it for these repositories again.
* To remove the assignments, select **Clear repository account assignments**. {% data variables.product.prodname_desktop %} asks you to choose an account the next time it needs credentials for these repositories.

![Screenshot of the "Sign out of @octocat?" window on Windows, with a "Clear repository account assignments" checkbox.](/assets/images/help/desktop/windows-sign-out-account-dialog.png)

1. Click **Sign out**.

{% endwindows %}

If the account’s token is no longer valid and {% data variables.product.prodname_desktop %} removes the account, the repository assignments are kept.

## Further reading

* [AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github-in-github-desktop)
Loading
Loading