We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
master
main
Nowadays it is more common to use the more inclusive term main for the default branch name (some context e.g. here https://www.theserverside.com/feature/Why-GitHub-renamed-its-master-branch-to-main and also https://github.com/github/renaming). I think it's also becoming a habit and needing to mentally switch between master and main (when most repos within our ecosystem and e.g. in CNCF use main) gets a bit annoying.
We should be only mindful of potentially breaking any integrations that depend on the default branch name.
The text was updated successfully, but these errors were encountered:
Hi, Can I take up this task?
Sorry, something went wrong.
No branches or pull requests
Nowadays it is more common to use the more inclusive term
main
for the default branch name (some context e.g. here https://www.theserverside.com/feature/Why-GitHub-renamed-its-master-branch-to-main and also https://github.com/github/renaming). I think it's also becoming a habit and needing to mentally switch betweenmaster
andmain
(when most repos within our ecosystem and e.g. in CNCF usemain
) gets a bit annoying.We should be only mindful of potentially breaking any integrations that depend on the default branch name.
The text was updated successfully, but these errors were encountered: