Context is pretty important when it comes to words with multiple definitions. I find it hard to interpret the "master branch" as anything but this definition. Now if you're talking about PATA hard drives, I can understand updating the standard terminology there.
Thats not the only definition though. It's clearly the intended one, but it's possible to make someone think of other definitions when a word pops up.
And it's not too hard to go "Oh, I get why alternate definitions might make people uncomfortable, even if I have no issue with it." And if you can see why someone might be uncomfortable in a situation, and it's zero effort to avoid that situation... why not?
Unless you're intentionally trying to not understand, or lack empathy and genuinely can't understand why words with alternate definitions heavily linked to slavery might make people uncomfortable, it feels pretty self explanatory.
I'll give Linus a pass, because linux kernel is probably the most widely accessed repo out there, and changing defaults and standards can have an actual impact on third party tooling.
It usually isn't, though. Going against a standard causes extra work. If it's an existing project that already used that "bad word" then you're proposing a major piece of work to change things around, likely breaking a ton of stuff in the process.
The meaning is exceedingly clear. Mindless actions ignoring context completely miss the entire point of the exercise, serving only to waste people's time with virtue signaling.
I in no way oppose changing the standard from "master" to "main" for new repositories, but going back and trying to change things with unknown dependencies is just going to cause more problems than it solves.
I genuinely can’t understand why words with alternate definitions linked to slavery might make people uncomfortable. It unintentionally reminds you bad things in history, and? Should we stop using words like "Nazi" or "War" too? Can we all stop using "death" while we're at it? It reminds me the mortal nature of human
And it’s not too hard to go “Oh, I get why alternate definitions might make people uncomfortable, even if I have no issue with it.”
If you accept the opinion of people that take your words out of context in order to get offended, somebody somewhere will have a problem with every word you can pick in a dictionary to use.
It's a power play. The people insisting on the change want to exploit the people doing things so that they gain some perceived or real reward. Stop supporting this.
People get super defensive about every single word they say, like some single solitary slight substitution squarely suggests stifling someone's soul, striking substance seemingly senselessly. But it's not substance: it's simply a choice of word that some/many make without even really considering it. It's a non-issue that suddenly becomes a big damn problem suppressing people's freeze peach for no good reason I recall ever seeing.
"Hey, could you not say [word] [/so much] maybe? There are [better/other] choices" is apparently equivalent in personal offensiveness to "You're now Harold, a Scientologist whose favourite colour is green and your greatest dream/goal in life is to become a glider pilot."
You had this problem probably because you created your repo with the GitHub web UI?
I always create the local repo first with git init, make at least 1 commit, and then gh repo create.
And yes, my default branch would be master but why should I care if I offend some Americans.