Changing your username
The following list contains limitations and considerations when changing your GitHub username. For the GitHub username policy, see Política de nome de usuário do GitHub.
Limitations of username changes
Members of an empresa com usuários gerenciados cannot change usernames. Your enterprise's IdP administrator controls your GitHub username. For more information, see Sobre os Enterprise Managed Users.
Se o namespace da conta inclui repositórios públicos que contêm uma ação listada no GitHub Marketplace ou que tinham mais de 100 clones ou mais de 100 usos do GitHub Actions na semana anterior à renomeação da sua conta, o GitHub desativa permanentemente a combinação antiga de nome do proprietário e do repositório (OLD-OWNER/REPOSITORY-NAME) quando você renomeia a sua conta. If you try to create a repository using a retired owner name and repository name combination, you will see the error: "The repository <REPOSITORY_NAME> has been retired and cannot be reused."
Se o namespace da conta incluir pacotes ou imagens de contêiner armazenados em um registro do GitHub Packages, o GitHub transferirá os pacotes e as imagens de contêiner para o novo namespace. Ao renomear a conta, você poderá interromper projetos que dependem desses pacotes. Se o namespace incluir imagens de contêiner que são públicas e têm mais de 5 mil downloads, o nome completo dessas imagens de contêiner (OLD-NAMESPACE/IMAGE-NAME) será desativado permanentemente quando você renomear a conta, para garantir que o nome da imagem de contêiner não possa ser reutilizado no futuro.
Repository redirects after username change
After you change your username, web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
Redirects for changed usernames
GitHub cannot set up redirects for:
Git commits after a username change
After a username change, verified commits signed using the previous GitHub-provided noreply email address will lose their "Verified" status.
When verifying a signature, GitHub checks that the email address of the committer or tagger exactly matches one of the email addresses associated with the GPG key's identities. Additionally, GitHub confirms that the email address is verified and linked to the user's account. This ensures that the key belongs to you and that you created the commit or tag. Because the username of the noreply email address changes, these commits can no longer be verified.
If you've been using a GitHub-provided private commit email address, whether or not your commit history will be retained after an account rename depends on the format of the email address. Git commits that are associated with your GitHub-provided noreply email address won't be attributed to your new username and won't appear in your contributions graph, unless your noreply email address is in the form of ID+USERNAME@users.noreply.github.com. Older versions of the noreply email address that do not contain a numeric ID will not be associated with your GitHub account after changing your username.