Regarding Git and Branch Naming

Regarding Git and Branch Naming

June 23, 2020

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.

Existing versions of Git are capable of working with any branch name; there’s nothing special about ‘master’ except that it has historically been the name used for the first branch when creating a new repository from scratch (with the git init command). Thus many projects use it to represent the primary line of development. 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 first step, Git will add a mechanism to allow users to specify the default used as the name of the first branch when creating a new repository. Also, consistent with its project governance, Git has undertaken a community process to explore changing the name of the first branch created automatically for new repositories away from ‘master’. That change is currently being discussed on our mailing list. As always, changes in Git’s core will minimize disruption for Git’s users and will include appropriate deprecation periods.

Meanwhile, Git as a project remains engaged in encouraging participation of underrepresented groups in the development of Git itself. Git continues their participation, which began four years ago, in Conservancy’s Outreachy initiative. Conservancy also continues to explore and support other initiatives that can also assist in this area.