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: September 2024
In September, we experienced three incidents that resulted in degraded performance across GitHub services.
Code referencing now generally available in GitHub Copilot and with Microsoft Azure AI
Announcing the general availability of code referencing in GitHub Copilot and Microsoft Azure AI, allowing developers to permit code suggestions containing public code matches while receiving detailed information about the match.
The nuances and challenges of moderating a code collaboration platform
Sharing the latest data update to our Transparency Center alongside a new research article on what makes moderating a code collaboration platform unique.