Repo Transfers
We’ve just opened up access to a feature we’ve been brewing for some time now… transferring repositories between accounts! While we’ve actually had this capability for a few months now,…
We’ve just opened up access to a feature we’ve been brewing for some time now… transferring repositories between accounts! While we’ve actually had this capability for a few months now, y’all had to contact support to request a repository move. Now you can do this yourself:

There are a few caveats of course, there always are…
- The target account must not have a repository with the same name, or a fork in the same network.
- If the repository is private the target account must have a paid account with at least one unused private repository available.
- Private forks cannot be transferred, only root private repositories.
We can’t set up redirects, so every clone of the repository will need to have it’s remote updated. Thankfully all you need to run is git remote set-url remote_name new_url to update your local repository.
Update
After much consideration and user feedback, we’ve decided to restrict this option a bit. You can now only transfer a repository into an organization account for which you have admin rights.
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.