I just used the most popular/known example. Personally I haven’t liked GitHub since Micro$oft bought them. I’m ol’ school, 25 years in the biz so M$ really really leaves a bad aftertaste in my mouth.
I’ll answer your other question in the other thread.
…but recommended to be changed every. single. time. you git init. https://lemmy.world/comment/11895670
No shit? Let me guess; you’re still using git like Linus intended it to be, decentralized, by emailing each other tar.gz’s
…which you get a multiline message telling you to change your ways (Linus doesn’t break UX)…every time you init…weird.
$ git init
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>
Parent/child(ren)(s)
unfair treatment.
We’re talking about slavery here.
sick of having to relabel
It’s not that hard…to be accommodating.
divorced from the social issues
from your point of view
the code doesn’t care
You’re right. Call it a controller and agent. I know naming is hard, but we’re smart enough to apply our lexicon.
never use the words master or slave ever again? What’s next??
Ah, the slippery slope fallacy.
We still use master over main
The default for new repositories on GitHub has been main for awhile now. You would have had to put in effort to change it to something else. You’re a stick in the mud.
unfair treatment.
We’re talking about slavery here.
sick of having to relabel
It’s not that hard…to be accommodating.
divorced from the social issues
from your point of view
the code doesn’t care
You’re right. Call it a controller and agent. I know naming is hard, but we’re smart enough to apply our lexicon.
never use the words master or slave ever again? What’s next??
Ah, the slippery slope fallacy.
We still use master over main
The default for repositories on GitHub has been main. You would have had to put in effort to change it to something else. You’re a stick in the mud.
I have no source to back this up so maybe I came up with this in my own reality, but I thought it was related to, pseudo = pretended.
Link to STL? (i kid, i kid)
Microsoft owns GitHub. The blast radius for this could be severe.
“I’m going to be annoying you until you do something about it” It is recommending that you take some sort of action, that choice is up to you as the user. In fact, the older way of disabling the warning was called
advice.defaultBranchNameAFAIK git is still Linus Trovalds’ project and one thing he is known for is “you dont fuckin break user space”. That is acknowledged in the pull request https://github.com/git/git/pull/921
Linus is also a fuck-your-feelings kind of guy so deprecation_period == linus_date_of_death. No, I’m not implying Linus is racist/bigot, just that he feels that strongly about breaking user experience.
You’re right…and that’s why its unbelievable to me how some people are still (it has been nearly 4 years since that PR above) resistant to change this one little thing. This is just the initial branch that we’re talking about here. Git doesn’t care if you:
git init Initialized empty Git repository in /home/xxxxxx/tmp/.git/ touch foo && git add foo && git commit -am "foo" [main (root-commit) 9c74dd1] foo 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 foo git branch -a * main git checkout -b bar Switched to a new branch 'bar' git branch -d main Deleted branch main (was 9c74dd1). git branch -a * bar git log commit 9c74dd18d493fec727e6ce9e4ba71ed356dd970d (HEAD -> bar) Author: Butters Date: Thu Aug 22 00:14:44 2024 -0400 foo