Cheatsheet for moving from Master to Main
Notes I have collected on how to renaming the Git default/primary branch
For my own reference, and anyone else interested in moving primary git branch from
I'm not interested in discussing reasons to do this here, it has been rehashed thousands of times already.
git branch -m master main # history unchanged git push origin HEAD git branch -u origin/main main
You can use https://github.com/ethomson/retarget_prs to do it.
Make sure you've pushed your
main branch, then head to
https://github.com/USERNAME/REPONAME/settings/branches - docs here
This is handy if you are working on local forks of OSS - Thanks to https://twitter.com/xunit/status/1269881005877256192
$ git branch --unset-upstream $ git branch -u origin/main
You can set new projects created on your machine to start with
main branch as well.
## Git 2.28+ git config --global init.defaultBranch main ## Git 2.27- git config --global alias.new '!git init && git symbolic-ref HEAD refs/heads/main'
This is for new projects on your local machine - unfortunately GitHub hasn't made a new setting for setting the default
main branch for new repos created on GitHub yet.
Edit: now it has! head to https://github.com/settings/repositories to set it
Lastly, you can setup bash aliases that tries
main first and then
master so you get to use the same alias no matter what you work with:
alias gpom="git push origin main 2> /dev/null || git push origin master"
If the GitHub process seem rather manual, don't worry. I have hundreds of repos on GitHub. GitHub has plans to release automated tooling to help you manage this.
- ✅ Jul 17 - redirects of deleted branches
- ✅ Aug 1 - GitHub Pages work from any branch
- ✅ Aug 26 - Be able to change default branch in Github
- ✅ Oct 1 - Default branch AUTOMATICALLY changes to
- Summer - Configurable default for new repos
- EoY 2020 - Retargeting PRs/Releases/Pages for existing repos