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
Take your local GitHub sessions anywhere
Kick off work in VS Code or the CLI, finish it from your phone. Remote control for GitHub Copilot sessions is now generally available on github.com and GitHub Mobile.
GitHub availability report: April 2026
In April, we experienced 10 incidents that resulted in degraded performance across GitHub services.
GitHub Copilot individual plans: Introducing flex allotments in Pro and Pro+, and a new Max plan
Starting June 1, our lineup of individual plans will update based on your feedback.