In the public discussion, a handful of different alternatives for "master" have popped up, "default" and "primary" being some of them. Fortunately, many people have become aware that this terminology (even more evident in "master/slave") should be replaced! The tech industry should move to a more inclusive, open culture - and removing language like "master/slave" is an important step in this journey. You can now rename any branch, including the default branch, from the web.For the longest time, the default branch in most Git repositories was named "master". We're using main for our newly-created repositories and for the repositories we're moving now, like dependabot-core. We like it because it's short, it keeps your muscle memory intact, and it translates well across most languages. Main is the most popular replacement for master that we're seeing across GitHub. Existing repositories are also not impacted by this change. Users, organizations, and enterprises that previously selected a default branch for new repositories are not impacted by this change. For enterprise administrators, on the page.The default branch name for new repositories created on GitHub is now main. New repositories use main as the default branch name We've updated Gists to use your preferred branch name.We've made it easier to rename an existing branch.GitHub Desktop has introduced a default branch setting for new repositories.Learn more about the new faultBranch setting in the Git 2.28 blog post. Git 2.28 added a similar setting to control the default branch used when you run git init on the command line. These settings cover repositories created through and the GitHub API.We're adding the same settings in the 3.0 release of GitHub Enterprise Server. We've added user, organization, and enterprise settings to set the default branch name for all newly-created repositories on.Pushing a new commit to the renamed branch will republish the site. Note: If the branch used by GitHub Pages is renamed, your GitHub Pages site will be unpublished.Note: publishing to the special gh-pages branch will still work the same as it always has, but now you can choose any other branch in your repository as the publishing source.
We've updated GitHub Pages to build and deploy from any branch.We've updated to redirect links that contain the deleted branch name such as master to the corresponding link in the repository's new default branch.We're making changes to GitHub in a few phases, designed to cause as little disruption to existing projects as possible.
#Git rename branch main code#
We're not the only organization in the Git ecosystem making these changes: there are upcoming changes in the Git project ( statement, code change), as well as coordinated changes from multiple vendors. This repository is our up-to-date guidance on how and when to rename your default branch. We're committed to making the renaming process as seamless as possible for project maintainers and all of their contributors.
GitHub is gradually renaming the default branch of our own repositories from master to main. Many communities, both on GitHub and in the wider Git community, are considering renaming the default branch name of their repository from master.
0 kommentar(er)
