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
Inside the research: How GitHub Copilot impacts the nature of work for open source maintainers
An interview with economic researchers analyzing the causal effect of GitHub Copilot on how open source maintainers work.
OpenAI’s latest o1 model now available in GitHub Copilot and GitHub Models
The December 17 release of OpenAI’s o1 model is now available in GitHub Copilot and GitHub Models, bringing advanced coding capabilities to your workflows.
Announcing 150M developers and a new free tier for GitHub Copilot in VS Code
Come and join 150M developers on GitHub that can now code with Copilot for free in VS Code.