Finally the old branch is deleted on the origin host.īecause of this change your fellow contributors will need to run the following commands in their local repository clones – This script is adapted from Scott Hanleman’s post.
The user is then prompted to make changes on the hosting site for the default branch (Instructions here for BitBucket, GitLab, and GitHub).Changes are then pushed to the remote, which does not have to be hosted on GitHub.Renames the old branch to the new branch (you can provide arguments to override the master and main defaults, as well as the default name of the remote origin).Makes sure that all changes for the old branch are pulled down and merged locally (if this fails the process stops).This should be run inside a local repository clone. Read -p "Press any key when the change is complete" x Follow the appropriate links for more information" Git pull || ( echo "pull failed, fix and run again" & exit 1 )Įcho "Please modify the default (or main) branch on your Git hosting server. # Run this script in a local repo to rename a branch and push the change to remote hosting service. I have created a Bash script, adopted from information and examples in various sources (mainly here and here), and you are welcome to adapt it. Making the change on existing repositories Developers (particularly on public projects) may get confused.Git Hook scripts may fail as well for the same reason.API calls on services like GitHub may not work if they have hard coded branch names.
GitHub will be automating this process later this year, but we didn’t want to wait. On our GitHub repos (public and private) we are changing master branch to main over the next few weeks. As part of the process PaperCut is examining our use of technical terms and labels as a small part of that change, so renaming the master branch in as many of our repos as possible seems like an obvious thing to do. These goals need to be addressed with real change. PaperCut needs to: authentically live our anti-racist values meet expecations in the broader community and, most importantly, respect our diverse colleagues and partners. I suspect if we were making the decision today, we’d pick another name, since that’s not what we want people to think of when they use Git" …“master”, even though from a different origin, brings the idea of human bondage and suffering to mind for a non-trivial number of people, which of course was not the intention and is undesirable. Carlson on the Git mailing list sums it up very nicely: You will find it useful to review GitHub’s corresponding release blog post and some of the linked documents. To that end rel 2.28 of Git now provides support to reconfigure the default. As part of this, the Git community has been doing some soul searching about using master as the default branch name in the git init command. Inline with the global Black Lives Matter movement, various developer communities have been looking at behaviours and language to see how we can all be more inclusive. Note that this blog post assumes you have already experience with Git, the world’s most popular version control tool. This post explains why, shows how we are approaching this, and gives some suggestions that might be useful if you want to make similar changes. TL DR: We are renaming our Git master branches to main.
0 kommentar(er)
