3 ms·

This is not a GitHub issue - Git itself now asks you if you would like to use the more inclusive `main`. I personally don't care for these changes, I will like

This is not a GitHub issue - Git itself now asks you if you would like to use the more inclusive `main`. I personally don't care for these changes, I will likely keep using `master` because I "automatically" type it in my workflow, and I find master to be a lot more descriptive. `main` is the name of my main.c, main.go or main.cpp file, the name of the main function, etc. I dont need another "main" to mess up my autocomplete. If they (github/microsoft) want to make a difference, I'm there with them, if they decide they want to put a few more millions a year towards getting lower-class children a higher education, I'm happily going to buy some GitHub pro or whatever. Until then, they need to step down and just be the tool they are, nothing more.

dgellow 6y ago
> This is not a GitHub issue - Git itself now asks you if you would like to use the more inclusive `main`. When does git asks this? From what I've seen, they just introduced a new config to change the name of the default branch, which is quite nice in itself (as of Git 2.28, released 27th July 2020). $ git config --global init.defaultBranch <NAME_OF_YOUR_DEFAULT_BRANCH>
JimDabell 6y ago
> Git itself now asks you if you would like to use the more inclusive `main`. No it doesn’t. It says this: hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name>