-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename default branch to main
#461
Comments
I am in favor of this renaming. It is "the right thing to do" as you note in the spirit of being an inviting and inclusive community. Moving to using "main" is an appropriate way to honor our own code of conduct. In my reading, the origin of the term "master" in this context is not -clearly- linked to "master/slave"; other will disagree and that is their prerogative. Most words have multiple meanings, and the interpretation and feelings behind any word or phrase are individualistic in nature. Individuals are how projects succeed or fail, and we want to embrace everyone to as high a degree as reasonably possible in their complexities, interpretations, and feelings. Based on this interpretation of the situation, renaming the primary branch we use from "master" to "main" makes complete sense. GIT and GitHub provide a means (1) move "master" to "main", and then (2) to "symlink" back from "main" to "master" to allow all current uses of those branch names to continue while we note the deprecation and eventual removal of the latter. I would approve of this method of renaming. |
So, to quickly write down what just happened:
So, further methodology is to abandon |
As discussed in chat: this was left open as a reminder, but with main being well-established now, can be closed. |
You might have seen or heard about projects renaming their default branch to
main
. We want to be an inviting and inclusive community and thus, it would be appropriate to rename our default branch.The GitHub docs describe how to rename the default branch. Further, it seems like there are already quite a few measures in place that help us avoid issues.
The text was updated successfully, but these errors were encountered: