Transition Steps
Step-by-step guide for developers to transition from Bitbucket to GitHub.
Transition Steps
For All Developers
- Before March 12 — Push all your branches and WIP to Bitbucket upstream
- Set up SSH keys for GitHub (see Prerequisites)
- After cutoff — Clone repos from GitHub and update your local remotes
Updating Your Local Remote
Once a repo is migrated, update your remote URL:
git remote set-url origin git@github.com:<org>/<repo>.gitVerify with:
git remote -vFAQ
Q: Can I still push to Bitbucket after March 12? A: No. After the cutoff, all new commits should go to GitHub.
Q: What if I have open PRs on Bitbucket? A: Merge or close them before the cutoff. Any unmerged work should be rebased onto the GitHub repo after migration.
Q: Do I need a new SSH key for GitHub? A: If you already have an SSH key, you can add the same public key to GitHub. You don't need to generate a new one unless you prefer to.