GitHub Change Username: What Redirects and What Breaks

A GitHub change username request takes one dialog box and a few seconds. Working out what it breaks takes longer. GitHub documents the answer across eight pages, and the short version is that your repositories mostly survive, your profile and gist links do not, and your old name goes straight back on the shelf for anyone to take. This guide covers every effect GitHub puts in writing, the list of things to update afterwards, and what the Username Policy actually says about names that look abandoned.

Everything quoted below is from GitHub Docs, linked where it first appears and read on 1 November 2026.

How to change your GitHub username

Two boundaries first. This covers a personal account; renaming an organization is a separate setting under that organization’s own “Danger zone”, with its own rename behaviour. And the author name on past commits comes from the Git metadata in those commits, not from your handle, so a rename does not rewrite it.

Where the setting lives: Settings > Account > Change username

GitHub’s guide to changing your username gives the path in three steps. In the upper-right corner of any page, click your profile picture, then click Settings. In the left sidebar, click Account. In the “Change username” section, click Change username.

You then get a warning screen. Read it rather than clicking through: the button is labelled I understand, let’s change my username. That click is an acknowledgement, not the rename; you still type the new name and confirm on the next screen.

Choosing a name that isn’t in use

Type the new name. If it is available, the Change my username button completes the swap. If it is not, GitHub offers you suggestions or you try something else. There is no queue, no reservation and no notification if the name you wanted frees up later.

Can you change back? GitHub documents no limit on how often you may rename, so a second rename is possible, but the old handle is yours again only if nobody claimed it meanwhile. Retired owner and repository name combinations, covered below, never come back.

A short checklist before you confirm

Before you click, collect four lists: every local clone on every machine you use, every CODEOWNERS file that names you, every public place your profile URL is published, and every script or pipeline that has your handle hard-coded. You will need all four within the hour.

What happens when you change your GitHub username

Your old username becomes available for anyone to claim

This is the fact everything else hangs on. GitHub’s page on username changes states that after the change, the old name becomes available for anyone else to claim. No cooling-off period is documented.

Underneath, the account record stays put, and the numeric account ID is the durable pointer to it: GitHub’s REST reference for users offers lookup by account ID rather than by login, because a login can change over time. What a rename does to the creation date is not documented, so do not treat it as settled. If you verify a GitHub account’s age from the public API, store the ID beside the date.

Repository web links and Git pushes to old remote URLs keep working

GitHub’s username reference says that after you change your username, web links to your existing repositories will continue to work, and that command line pushes from your local repository clones to the old remote tracking URLs will continue to work as well.

So a stale git push from a forgotten laptop will not fail the morning after a rename. That is a grace period, not a guarantee.

How a new repository under your old name overrides a redirect

Here is the failure mode. Someone claims your released name. They create a repository called the same thing as one of yours. GitHub’s documentation is blunt about the result: that will override the redirect entry and your redirect will stop working.

Nothing warns you. The link simply starts resolving to a stranger’s repository, which is worse than a 404 for anything documented, published or depended on.

Permanent retirement of popular owner and repository name combinations

Some combinations never come back. GitHub’s username reference says that where a public repository contained an action listed on GitHub Marketplace, or had more than 100 clones, or more than 100 uses of GitHub Actions in the week prior to the rename, GitHub permanently retires the old owner name and repository name combination.

The same reference extends the rule to packages: public container images with more than 5,000 downloads also have their full former name permanently retired.

The rule protects consumers of popular actions and images from a replacement at a trusted path, and it means the old URL is permanently dead rather than permanently yours.

GitHub change username side effects that break links

These are the GitHub change username side effects nobody budgets time for.

Profile URLs under the old name return 404

Links to your old profile page stop working and return a 404 error. Every conference bio, README badge, CV, package author field and portfolio link pointing at the old handle is now dead.

Gist URLs change and old gist links return 404

Gist URLs include your username, so they change with it, and earlier links to them return 404. GitHub states plainly that it cannot set up redirects for gists that include your old username. If you have ever pasted a gist into an issue, a blog post or a Stack Overflow answer, those references are now broken.

@mentions of the old username don’t redirect

GitHub also cannot redirect @mentions using your old name. Historical mentions across issues, pull requests and discussion threads stay pointed at a handle that is no longer yours, and will point at a stranger if someone claims it.

GitHub Mobile may show the old name until you log out

A small one that causes real confusion: accounts logged in to GitHub Mobile may continue to display your original username until you log out. Sign out and back in on each device so you are not debugging a cache.

GitHub change username consequences for commits

Commit attribution is where the GitHub change username consequences get subtle, because the answer depends on which email address made the commit.

Commits tied to email addresses on your account stay attributed

Commits associated with another email address you have added to your account continue to be attributed to you and appear in your contributions graph. If you commit with a real address listed in your account’s email settings, the rename changes nothing.

Commits that used GitHub-provided noreply addresses

Commits made with a GitHub-provided address may be affected. The split is the numeric ID. Older noreply formats that do not contain a numeric ID will not be associated with your account after the change, so those commits are not attributed to your new username and do not appear in your contributions graph. Addresses in the ID+USERNAME@users.noreply.github.com form survive, because the ID identifies the account rather than the name.

Verified commits signed with the old noreply address lose Verified status

Signed commits have one more consequence. Commits signed using your previous GitHub-provided noreply address lose their “Verified” status, because those commits can no longer be verified. The history is intact; the badge is not. If signature status matters to your project, note which commits are affected before you rename rather than discovering it in a review.

What to update after the rename

git remote set-url on every local clone

Do not live on the redirect. GitHub’s guide to managing remote repositories documents the fix, and it is one command per clone:

git remote -v
git remote set-url origin https://github.com/OWNER/REPOSITORY.git
git remote -v

Run git remote -v afterwards to confirm both the fetch and push lines now carry the new owner. Repeat on every machine, including build agents and any server with a working copy.

CODEOWNERS files that name the old username

GitHub states that CODEOWNERS files listing your old username will need to be updated manually. Nothing rewrites them for you, and a CODEOWNERS entry pointing at a name you no longer hold silently stops requesting your review.

Links on websites, profiles and documentation

Work through the public surface: your site, your package metadata, your social profiles, your README badges, your talks and anything you have published that embeds a profile or gist URL. These are the links that now return 404 rather than redirecting.

Any configuration or script that contains the old name

GitHub’s documentation describes the areas above. It does not describe what a rename does to every other part of your setup, so do not assume behaviour there. Instead, grep your own configuration for the old string: CI definitions, deployment scripts, webhook targets, package and image references beyond the retirement rule above, and anything that builds a URL from a handle.

This is also the moment to check automation credentials. If a bot account is involved, the right credential is often not a renamed user at all, and the trade-offs between a GitHub App, a machine account and a deploy key are worth a read before you rebuild anything around a username.

GitHub inactive username: can you claim one?

The GitHub inactive username question has a short answer, and people do not like it.

What GitHub’s Username Policy says about names that look unused

The GitHub Username Policy addresses this directly: “We do not accept requests to release, transfer, or reclaim usernames on the basis that they appear inactive or unused.”

So the common plan — find a handle with no commits since 2014, open a support ticket, wait — does not work. There is no process behind it to wait for.

Name squatting and why names can’t be held for later

The same policy removes the opposite move: “GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use.” Registering spare accounts to park names you might want is itself against the rules.

Trademark complaints: the only release requests GitHub reviews

One exception exists, and it is narrow. The policy states: “Valid trademark-related complaints are the only requests we review for possible release of a username that is already claimed.” If you own the mark, that complaint route is the only door. Liking the name is not a trademark claim.

Buying or selling account names is prohibited

There is no private market either. The Username Policy prohibits attempts to sell, buy or solicit payment of any kind in exchange for account names, and warns that doing so may result in permanent account suspension. A handle bought in a direct message can be reclaimed by GitHub at any point, and the buyer has nothing to appeal with.

GitHub delete account: what happens to the username

The GitHub delete account route releases a name too, just more slowly.

The username becomes available to others after 90 days

GitHub’s personal account reference states that your username will be available for anyone to use after 90 days. That delay is the only difference from a rename, and it is not a reservation you can extend.

Repositories, packages and retired names when an account is deleted

Deletion is destructive. Repositories, forks of private repositories, wikis, issues and pull requests owned by the account are deleted, as are GitHub Pages sites, and packages and container images in a GitHub Packages registry go with them, which breaks anything that depended on those paths. Some names never return: GitHub permanently retires the owner name and repository name combination for public repositories that contained a Marketplace action or that had more than 100 clones or more than 100 uses of GitHub Actions in the week prior to deletion, and public container image names with more than 5,000 downloads are permanently retired as well.

If you are renaming because you want a clean start, rename. Deleting costs you the history and still does not hand anyone the name faster than three months.

A note on GitHub accounts from PVAVRT

Almost everyone reading this is renaming the one free account GitHub’s Terms allow them, and the checklist above is the whole job. A smaller group manages several logins for a team, which is the only place PVAVRT’s catalog touches this topic.

Two points belong here plainly. Buying accounts breaks GitHub’s terms, and GitHub can suspend access at any time, so an account you did not create is a poor place to keep anything you would mind losing. And a GitHub handle is never part of a purchase: the Username Policy quoted above rules out paying for a name. If what you actually need is automation rather than extra logins, the free, documented routes above cover most of it.

PVAVRT keeps a GitHub accounts page, the two points above apply to anything bought there, and what GitHub’s terms allow before you buy goes through those rules in more detail. Rename your own account with the checklist above first; if you still have questions about that page, send them to Telegram @pvavrt and say what the accounts are for.