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: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.