Repository redirects are here!
It’s a fact of life – sometimes repository names change. This can happen in a few different types of scenarios: When you rename a repository. When you rename your user…
It’s a fact of life – sometimes repository names change. This can happen in a few different types of scenarios:
- When you rename a repository.
- When you rename your user or organization account.
- When you transfer a repository from one user or organization to another.
We’re happy to announce that starting today, we’ll automatically redirect all requests for previous repository locations to their new home in these circumstances. There’s nothing special you have to do. Just rename away and we’ll take care of the rest.
As a special bonus, we’ll also be servicing all Git clone, fetch, and push requests from previous repository locations.
There is one caveat with the new redirect support worth noting: GitHub Pages sites are not automatically redirected when their repositories are renamed at this time. Renaming a Pages repository will continue to break any existing links to content hosted on the github.io domain or custom domains.
Written by
Related posts
GitHub availability report: June 2026
In June, we experienced six incidents that resulted in degraded performance across GitHub services.
Q1 2026 Innovation Graph update: Open source collaboration is accelerating worldwide
New Innovation Graph data shows global developer communities growing faster than ever, with collaboration reaching new highs across many economies.
GitHub joins coalition advocating for fixes to California AI Transparency Act to protect open source
We’re calling for targeted amendments to resolve conflicts with open source licensing and align with international transparency frameworks while preserving regulatory intent.