It seems that fewer and fewer repositories are keeping their default branch as "master". It leads to very weird conversations (https://github.com/cookiecutter/cookiecutter/issues/1735) and I think that as a UN tool we should protect ourselves from any backfire. FYI it's now included in the Python software foundation code of conduct and the one from the Mozilla foundation.
Is it a priority? no
when is the best moment to do it ? summer when nobody makes changes
In Github, it's super easy, once you change, all the forks and current PR will be pointing towards "main" and a message will be displayed to the newcomers to explain how to change the local name.
It seems that fewer and fewer repositories are keeping their
defaultbranch as "master". It leads to very weird conversations (https://github.com/cookiecutter/cookiecutter/issues/1735) and I think that as a UN tool we should protect ourselves from any backfire. FYI it's now included in the Python software foundation code of conduct and the one from the Mozilla foundation.Is it a priority? no
when is the best moment to do it ? summer when nobody makes changes
Here is an article explaining some of the reasons: https://www.theserverside.com/feature/Why-GitHub-renamed-its-master-branch-to-main
In Github, it's super easy, once you change, all the forks and current PR will be pointing towards "main" and a message will be displayed to the newcomers to explain how to change the local name.
My only concern is jenkins.