Change branch name to main

[cdce8p]

Typeshed just changed the name of the default branch from master to main python/typeshed#8956.
With the upcoming 1.0 release (#13685), I think it could make sense to do that for mypy, too.

Github does make it quite easy so we would likely only need to update a few references.
Besides that contributors would need to run these commands to update their local copy

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

[denballakh]

I don't think it's worth it. What's wrong with master?
If this is changed, then nothing good will happen, there will only be inconvenience for some contributors.

[sobolevn]

Both cpython and typeshed are using main now. I think it will be more consistent.

However, I am not a native english speaker, both of these words mean nothing to me. In my language master is someone who is good at something.
So, I don't really care.

[antonagestam]

The reasons as to why this change of terminology matters are well documented and debated already and shouldn't really need repeating here at this point, for y'all failing to use Google:

• https://dev.mysql.com/blog-archive/mysql-terminology-updates/
• https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/
• https://www.wired.com/story/tech-confronts-use-labels-master-slave/
• https://www.allaboutcircuits.com/news/how-master-slave-terminology-reexamined-in-electrical-engineering/
• https://www.drupal.org/project/drupal/issues/2275877
• #22667 replaced occurrences of master/slave terminology with leader/follower django/django#2692
• https://github.com/bitnami/bitnami-docker-postgresql/issues/175

Yes, this is "just" language, so let's just make the change and get on with our lives. Can we please just learn from where all these discussions have landed, and not repeat them again all over?

[JukkaL]

I'm fine with changing the branch name to main, but let's wait until 1.0 and any 1.0.x point releases are out to avoid disruption, i.e. let's do it between release cycles. 1.0 should be out within a month or so.

[cdce8p]

I'm fine with changing the branch name to main, but let's wait until 1.0 and any 1.0.x point releases are out to avoid disruption, i.e. let's do it between release cycles. 1.0 should be out within a month or so.

Maybe now could be a good time to do it. 1.3 has been out for two weeks and it doesn't look like 1.3.1 is necessary. Furthermore, the release-1.4 branch hasn't been cut yet.

Anyhow, the impact should be quite minimal. We'll probably only need to update the branch name in the Github actions workflow files and the readthedocs config. Links should continue to work although we could update these as well, of course.

mypy/.github/workflows/test.yml

Line 6 in cbf1665

branches: [master, 'release*']

[hugovk]

Some other bits:

CREDITS
5:https://github.com/python/mypy/commits/master

README.md
105:python3 -m pip install -U https://github.com/python/mypy/zipball/master

.github/PULL_REQUEST_TEMPLATE.md
7:- Read the [Contributing Guidelines](https://github.com/python/mypy/blob/master/CONTRIBUTING.md)

docs/source/extending_mypy.rst
96:`mypy/plugin.py <https://github.com/python/mypy/blob/master/mypy/plugin.py>`_
98:located in `mypy/plugins <https://github.com/python/mypy/tree/master/mypy/plugins>`_.

mypy/errors.py
1153:        "Please try using mypy master on GitHub:\n"
1162:            "If this issue continues with mypy master, "

mypyc/doc/dev-intro.md
66:the [mypy docs](https://github.com/python/mypy/blob/master/README.md).

[cdce8p]

I opened two PRs to help with the transition

• Update workflows to trigger for main #15310
  Should be merged before the branch name is changed!
• Cleanup reference to master branch #15311

[hugovk]

I'm fine with changing the branch name to main, but let's wait until 1.0 and any 1.0.x point releases are out to avoid disruption, i.e. let's do it between release cycles. 1.0 should be out within a month or so.

Mypy 1.7 was just released! 🎉

Is now a good time to flip the switch?