Changing your username
The following list contains limitations and considerations when changing your GitHub username. For the GitHub username policy, see Politique de nom d'utilisateur GitHub.
Limitations of username changes
Members of an entreprise avec utilisateurs managés cannot change usernames. Your enterprise's IdP administrator controls your GitHub username. For more information, see À propos d’Enterprise Managed Users.
Si l’espace de noms du compte inclut des dépôts publics qui contiennent une action listée sur GitHub Marketplace ou qui comptabilisent plus de 100 clones ou plus de 100 utilisations de GitHub Actions au cours de la semaine précédant le changement de nom de votre compte, GitHub met définitivement hors service l’ancienne combinaison nom de propriétaire et nom de dépôt (OLD-OWNER/REPOSITORY-NAME) quand vous renommez votre compte. 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."
Si l’espace de noms du compte inclut des packages ou des images conteneur stockées dans un registre GitHub Packages, GitHub transfère les packages et les images conteneur vers le nouvel espace de noms. En renommant votre compte, vous pouvez perturber des projets qui dépendent de ces packages. Si l’espace de noms inclut des images conteneur qui sont publiques et ont plus de 5 000 téléchargements, l’ancien nom complet de ces images conteneur (OLD-NAMESPACE/IMAGE-NAME) est définitivement abandonné lorsque vous renommez le compte pour garantir que le nom de l’image conteneur ne peut pas être réutilisé à l’avenir.
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.