Personal account management

About converting your personal account

Converting a personal account into an organization allows you move to a shared account where a large number of people can collaborate across many projects at once. 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
• For personal accounts on GitHub Pro, automatically transitions billing to the paid GitHub Team without the need to re-enter payment information, adjust your billing cycle, or double pay at any time

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 Роли в организации.

To convert your personal account into an organization, see Преобразование пользователя в организацию.

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. 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.

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.

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.

• Передача владения организацией
• Удаление учетной записи организации
• Удаление себя из организации
• Personal account reference

To delete your personal account, see Удаление личной учетной записи.

About unlinking your email address

Since an email address can only be associated with a single GitHub 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 Указание адреса электронной почты для фиксаций.

Be aware that nothing else associated with your 2FA locked account, including your repositories, permissions, and profile, will transfer to your new account.

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.

To unlink an email address, see Отмена связывания адреса электронной почты из заблокированной учетной записи.

About management of multiple accounts

In some cases, you may need to use multiple accounts on 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.

To learn how to manage multiple accounts, see Управление несколькими учетными записями.

You cannot use a управляемая учетная запись пользователя to contribute to public projects on GitHub.com, so you must contribute to those resources using your personal account. For more information, see About Enterprise Managed Users in the GitHub Enterprise Cloud documentation.

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 Переключение между учетными записями.

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.

If you aren't required to use a управляемая учетная запись пользователя, GitHub recommends that you use one personal account for all your work on GitHub.com. 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.

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 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 Клонирование репозитория.

For more information about the use of SSH to access repositories, see Подключение к GitHub с помощью SSH.