1
0
mirror of synced 2025-12-25 02:17:36 -05:00

[EDI] Managing your personal account (#57153)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>
This commit is contained in:
Steve Ward
2025-09-02 14:29:51 -04:00
committed by GitHub
parent 6ad5382356
commit 294e6015d9
9 changed files with 146 additions and 103 deletions

View File

@@ -19,23 +19,6 @@ topics:
shortTitle: User into an organization
---
> [!WARNING]
> Before converting a user into an organization, keep these points in mind.
>
> * You will **no longer** be able to sign into the converted personal account.
> * You will **no longer** be able to create or modify gists owned by the converted personal account.
> * An organization **cannot** be converted back to a user.
> * The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
> * Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
> * Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
> * Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
> * Any forks of private repositories made with the converted personal account will be deleted.
> * Since organizations cannot star repositories, you will no longer have access to your original list of starred repositories.
> * You will no longer have access to the list of users you were following from your user account.
> * Any followers of your user account will not automatically follow the new organization.
> * Any existing collaborators on your projects will still have access to those projects in the new organization.
> * {% data variables.product.prodname_actions %} is not automatically enabled on the account after converting it to an organization, and will have to be re-enabled. To re-enable {% data variables.product.prodname_actions %}, create a new workflow file in the `.github/workflows` directory of your repository.
## Prerequisites
The personal account you want to convert cannot be a member of any organizations. If the personal account you want to convert is a member of an organization, you must leave the organization before you can convert the account.
@@ -54,16 +37,9 @@ If you want your organization to have the same name that you are currently using
## Convert your personal account into an organization automatically
You can also convert your personal account directly into an organization. Converting your account:
* Preserves the repositories as they are without the need to transfer them to another account manually
* Automatically invites collaborators to teams with permissions equivalent to what they had before
{%- ifversion fpt or ghec %}
* For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/billing/managing-the-plan-for-your-github-account/about-billing-for-plans) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time
{%- endif %}
To convert your personal account into an organization, follow these steps:
When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as outside collaborators. You can then invite outside collaborators to become members of your new organization if you wish. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).
1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
1. Create a new personal account, which you'll use to sign into {% data variables.product.github %} and access the organization and your repositories after you convert.
1. [Leave any organizations](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) the personal account you're converting has joined.
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.organizations %}
@@ -74,8 +50,9 @@ When you convert a personal account into an organization, we'll add collaborator
1. Click **Create Organization**.
1. Sign in to the new personal account you created earlier, then use the context switcher to access your new organization.
## Further reading
## Next steps
* [AUTOTITLE](/account-and-profile/reference/personal-account-reference#side-effects-of-converting-an-account-to-an-organization)
* [AUTOTITLE](/organizations/organizing-members-into-teams)
{% ifversion fpt or ghec %}
* [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)

View File

@@ -18,18 +18,6 @@ topics:
shortTitle: Delete your account
---
## About deletion of your personal account
Deleting your personal account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted. Your resources and comments will become associated with the [ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}
{% ifversion fpt or ghec %}
{% data reusables.accounts.delete-account-repo-namespace-retirement %}
{% endif %}
{% data reusables.package_registry.delete-account-namespace-retirement %}
{% ifversion ghec %}
> [!NOTE]
@@ -37,37 +25,28 @@ Deleting your personal account removes all repositories, forks of private reposi
{% endif %}
{% ifversion fpt or ghec %}When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account. After 90 days, the account name also becomes available to anyone else to use on a new account.{% endif %}
If you're the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your personal account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your personal account.
For more information, see the following articles.
* [AUTOTITLE](/organizations/managing-organization-settings/transferring-organization-ownership)
* [AUTOTITLE](/organizations/managing-organization-settings/deleting-an-organization-account)
* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization)
{% ifversion ghes %}
> [!NOTE]
> * You should contact an enterprise owner before deleting your account on {% data variables.product.prodname_ghe_server %}.
{% endif %}
## Back up your account data
Before you delete your personal account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account. For more information, see [AUTOTITLE](/repositories/archiving-a-github-repository/backing-up-a-repository).
Before you delete your personal account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account. For more information, see the following articles:
* [AUTOTITLE](/repositories/archiving-a-github-repository/backing-up-a-repository).
* [AUTOTITLE](/account-and-profile/reference/personal-account-reference#side-effects-of-account-deletion)
## Deleting your personal account
> [!WARNING]
> Once your personal account has been deleted, {% ifversion fpt or ghec %}{% data variables.product.company_short %}{% elsif ghes %}an enterprise owner{% endif %} cannot restore your content.
## Deleting your personal account
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.account_settings %}
1. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your personal account:
* If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
* If there are other organization owners in the organization, you must remove yourself from the organization.
1. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
{% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted. Your billing will end immediately. Your username will be available for anyone to use after 90 days.{% else %}
* Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use.{% endif %}
* In the first field, type your username or email.
* In the second field, type the phrase from the prompt.

View File

@@ -12,31 +12,6 @@ redirect_from:
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts
---
## About management of multiple accounts
In some cases, you may need to use multiple accounts on {% data variables.product.github %}. For example, you may have a personal account for open source contributions, and your employer may also create and manage a user account for you within an enterprise.
You cannot use a {% data variables.enterprise.prodname_managed_user %} to contribute to public projects on {% data variables.location.product_location %}, so you must contribute to those resources using your personal account. For more information, see [About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts){% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}.{% endif %}
If you need to use multiple accounts, you can stay signed in to your accounts and switch between them. For example, switching between a personal account and a service account. For more information, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/switching-between-accounts).
If you want to use one workstation to contribute from both accounts, you can simplify contribution with Git by using a mixture of protocols to access repository data, or by using credentials on a per-repository basis.
> [!WARNING]
> Be mindful when you use one workstation to contribute to two separate accounts. Management of two or more accounts can increase the chance of mistakenly leaking internal code to the public.
If you aren't required to use a {% data variables.enterprise.prodname_managed_user %}, {% data variables.product.company_short %} recommends that you use one personal account for all your work on {% data variables.location.product_location %}. With a single personal account, you can contribute to a combination of personal, open source, or professional projects using one identity. Other people can invite the account to contribute to both individual repositories and repositories owned by an organization, and the account can be a member of multiple organizations or enterprises.
## Contributing to two accounts using HTTPS and SSH
If you contribute with two accounts from one workstation, you can access repositories by using a different protocol and credentials for each account.
Git can use either the HTTPS or SSH protocol to access and update data in repositories on {% data variables.product.github %}. The protocol you use to clone a repository determines which credentials your workstation will use to authenticate when you access the repository. With this approach to account management, you store the credentials for one account to use for HTTPS connections and upload an SSH key to the other account to use for SSH connections.
You can find both the HTTPS or an SSH URLs for cloning a repository on the repository's page. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository).
For more information about the use of SSH to access repositories, see [AUTOTITLE](/authentication/connecting-to-github-with-ssh).
## Contributing to multiple accounts using HTTPS and {% data variables.product.pat_generic %}s
Alternatively, if you want to use the HTTPS protocol for both accounts, you can use different {% data variables.product.pat_generic %}s for each account by configuring Git to store different credentials for each repository.

View File

@@ -30,12 +30,6 @@ shortTitle: Merge multiple accounts
{% endif %}
> [!WARNING]
> * Organization and repository access permissions aren't transferable between accounts. If the account you want to delete has an existing access permission, an organization owner or repository administrator will need to invite the account that you want to keep.
> * Any commits authored with a {% data variables.product.company_short %}-provided `noreply` email address cannot be transferred from one account to another. If the account you want to delete used the **Keep my email address private** option, it won't be possible to transfer the commits authored by the account you are deleting to the account you want to keep.
> * Issues, pull requests, and discussions will not be attributed to the new account.
> * Achievements are not able to be transferred between accounts.
1. [Transfer any repositories](/repositories/creating-and-managing-repositories/transferring-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
1. [Update the remote URLs](/get-started/git-basics/managing-remote-repositories) in any local clones of the repositories that were moved.
1. [Delete the account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account) you no longer want to use.
@@ -43,7 +37,8 @@ shortTitle: Merge multiple accounts
> [!NOTE]
> There are additional requirements for commits to count as contributions that you will need to ensure are met. See [AUTOTITLE](/account-and-profile/reference/why-are-my-contributions-not-showing-up-on-my-profile#contribution-criteria-for-commits).
## Further reading
## Next steps
* [AUTOTITLE](/account-and-profile/reference/personal-account-reference#side-effects-of-merging-accounts)
* [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts)
* [AUTOTITLE](/account-and-profile/reference/best-practices-for-leaving-your-company)

View File

@@ -13,21 +13,6 @@ topics:
shortTitle: Unlink your email
---
## About unlinking your email address
Since an email address can only be associated with a single {% data variables.product.prodname_dotcom %} account, when you've lost your 2FA credentials and are unable to recover access, unlinking your email address from the locked account allows you to link that email address to a new or existing account. Additionally, linking a previously used commit email address to a new account will connect your commit history to that account. Unless you have chosen to keep your email address private, your account's commit email address is the same as your account's primary email address. See [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).
> [!NOTE]
> The {% data variables.product.github %}-provided `noreply` email address cannot be unlinked from an account. Commits authored with a `noreply` address cannot be reconnected to a different account.
Be aware that nothing else associated with your 2FA locked account, including your repositories, permissions, and profile, will transfer to your new account.
## Unlinking your email address
Unlinking email addresses is only available for accounts with 2FA enabled. If you do not have 2FA enabled, you can sign in and remove your email address from your account settings.
Educational benefits cannot be transferred after an email address is unlinked and associated with a different account. To keep these benefits, you must continue using the original account that was used to apply.
> [!WARNING]
> Following these steps will not disable 2FA or provide access to a locked account, but will instead unlink the associated email address so it may be used for a different account. If you cannot regain access to the 2FA locked account, these steps will permanently break the link between the account and the linked email address. Before continuing, be sure you have lost all access to your account. See [AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials).