Closed skalish closed 3 years ago
Github has guidance for changing the default branch name.
Note that they claim to "make it seamless for existing repositories to rename their default branch. When you rename the branch, we’ll retarget your open PRs and draft releases, move your branch protection policies, and more - all automatically" by "later this year" (see seamless move for existing repositories)
For instructions on updating your forks, see Easily rename your Git default branch from master to main, namely:
git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main
replacing origin
with the git remote that corresponds to your fork.
:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on:
v1.3.0
Your semantic-release bot :package::rocket:
We should follow through on a commitment to change the default branch name of the repo from the problematic name
master
to the Github-recommended namemain
.