![]() ![]() ![]() Next steps to be taken by every team member after the orchestrator, conductor, or administrator performs the renameĪfter the orchestrator, conductor, or administrator performs the above steps everyone who uses the given repository will need to make sure they have the newly renamed main branch and have deleted their old copy of the branch named master. Change "Main branch" from master to main.Assuming you've pushed main from the steps above.In a local terminal on your local computer, do the following (this should be done by one person, think of this person as the orchestrator, conductor, or administrator for this process): git branch -move master mainĪfter executing the two above, the orchestrator, conductor, or administrator should then perform the following steps on BitBucket: Here is the process as excerpted from DEV: Change Git's Default Branch From Master: First, again have your team merge any outstanding PRs into your master branch. You will not be able to complete this process without those permissions. To do these activities you will need administrative permissions on the given repository. Still I tend to wait until one sprint has ended and the other has not started and all outstanding PRs have been merged into master and no new branches have been cut from master or any branches cut from master. Basically you will be renaming the master branch to main and then in BitBucket changing the default branch from master to main. The process/steps involved are pretty easy. GitHub to replace master with main starting in October: What developers need to do now | TechRepublic.GitHub to replace 'master' with 'main' starting next month | ZDNET.Here are the other two links on this topic: GitHub took action based on the Conservancy's suggestion and moved away from the term master when a Git repository is initialized, "We support and encourage projects to switch to branch names that are meaningful and inclusive, and we'll be adding features to Git to make it even easier to use a different default for new projects." As a result, GitHub renamed the master branch to main branch. "Both Conservancy and the Git project are aware that the initial branch name, 'master,' is offensive to some people and we empathize with those hurt by the use of that term," said the Software Freedom Conservancy. Amid the many protests and the growing social unrest, these harmful and antiquated terms were no longer considered appropriate. The computer industry's use of the terms master and slave caught everyone's attention in the summer of 2020. Additionally, I believe we can change our default in BitBucket to main.įrom The Server Side: Why GitHub renamed its master branch to main: Cultural sensitivity I have renamed master to main several times and it is not difficult. One an article from ZD-NET, another from TechRepublic, and a third from The Server Side. I have included three links on this topic. ![]() Throughout many technology companies there has been a movement to eliminate divisive language in favor of non-divisive language, this includes eliminating the use of terms that were inappropriately and offensively taken from slavery including the elimination of the term master in favor of main. ![]()
0 Comments
Leave a Reply. |