As long as changing the name of the default branch in a Git repo is worthy of the front page of Hacker News: I also changed my defaults this year. My muscle memory has changed so that “main” is now what I expect. I’ll just go with the flow and change the name of a branch whenever I trip over it.

> We've chosen main specifically as it's the default for newly-created repositories in GitHub and the renaming will leverage the GitHub tooling built to make this easier.

Suuuuure.

The original master -> main folks should have been laughed out of the room the first time around. At this point it's a religion.

The anti-“master” argument feels pretty weak to me, but just as weak as the vehement opposition feels hidebound. It’s a name of a thing. If it changing it makes more people happy and likely to contribute, why not.

I set my default name to trunk because it makes sense. Main makes no sense.

I think it is generally not worth to change the names of the existing branches, including probably this one, but it might not be a problem. As far as I know, changing branch names in git does not change the hashes (and the name "main" does not consist entirely of hex digits, etc), so it should probably be OK, although still something I personally would probably not have done. (I would have no problems with making the default branch name "main" for a new repository rather than an existing one, although I prefer "trunk")