Changing your username
The following list contains limitations and considerations when changing your GitHub username..
Limitations of username changes
If you sign into your GitHub Enterprise Server instance with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for GitHub Enterprise Server, see Understanding IAM for enterprises.
If the account namespace includes any packages or container images stored in a GitHub Packages registry, GitHub transfers the packages and container images to the new namespace. By renaming your account, you may break projects that depend on these packages.
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.