Hit me up on twitter: or send me an email.Created: January-20, 2022 | Updated: February-06, 2022 GitHub is also working on it says Nat Friedman. in both om/ and, official maintainers of Git are working to find a new name and incorporate it into the culture of the product. Are they changing Git to do this by default? Sadly, it’s best if you repeat this procedure each time you create a new repo … for now. There are some kludgy workarounds for getting Git to automatically create the main branch instead of the master branch, but they’re awkward at best and not durable to Git version upgrades. Can I make this the default for new repos? If you have automation around branch names, you may need to change Jenkins or GitHub Actions to tell the build that it should look to main rather than master. You may consider naming it prod instead of main. You likely still need to create main and remove master, but you don’t need to change the default branch.
If you’re using GitFlow or GitHub Flow or another branch naming strategy, your default branch may be develop or dev or similar. Sadly, there’s no way to create a pull request to change the default branch. If you began this repository by forking another GitHub repo, you can make this change on your copy, but you’ll need to petition the maintainers to make this change on the main repository. This says roughly “go delete all my local pointers to the remote branches that no longer exist.” If you’re on any other branch such as develop or a feature branch, skip this step. If you’re currently on master, switch to the new branch: If you’re on the master branch when you do, you may get an error, so instead: But they will need to change their own repository. We’ve already changed the server, so they won’t need to do that. Verify the change locally by running git log -oneline -graph -decorate -all and also verifying master is gone. Verify the change by refreshing the main repository page on GitHub and noting that main loaded by default, and that master is nowhere to be found. The : is the magic sauce that removes the branch from the server. If it complains that the branch is not fully merged, you may need to merge master into main first: git checkout main git merge master git branch -d master This warning helps us understand that we’ll close any open pull requests against master and potentially affect any cloned or forked repositories. On GitHub, select settings, branches, and in the drop-down pick main.Ĭlick OK to the warning. This gets the branch up on GitHub, but doesn’t yet make it the default. We can also see origin/master, the reference on GitHub. We can see the master branch, and HEAD is pointing to this branch. When we clone the repository, this is the branch we’ll first have checked out. The default branch is the one shown when we first load GitHub, the README.md is shown below our code.
Let’s transition a repository that’s shared among our team. Is your goal to make a change or to make a statement? Change default branch on GitHub We can verify the change is made successfully:Īfter all, no one will notice. This creates the new branch and checks it out at the same time. Open a terminal in the repository and let’s get the current log: Maybe this repo is for a personal pet project, or maybe it’s an experiment that we did quickly. Let’s transition a local repository that isn’t pushed anywhere. Let’s look at two scenarios: changing a local repository, and changing a repository on GitHub. Renaming the default branch in Git from master to main is easy.
0 kommentar(er)
