Why not call it trunk and make it all tree themed
Cause git doesn’t work that way. There is no trunk. It’s all branches.
But that’s not actually true in general; there is a default branch concept in forges, and an integration and/or release branch in most recommended workflows. That’s the trunk.
What is a trunk if not a large branch
Oh, that’s valid, and forks could be called “asexual propagation”
Cherry picking from one trunk to another could be called grafting.
There is already pruning.
If there is no AI used, it could be called GMO.
I’m not sure if there is a tree analogy for merging trunks together, however.
Someone suggested queen and worker. Luffy and then branches named after crew members also seemed nice. Another suggested dom and sub. Leader and cultist were other suggestions. For any StarCraft mod it should be Kerrigan and Raynor, or OverMind and Zerg, or for the later stages Amon and Protoss.
I love all those suggestions. Keeps things interesting and conveys the same thing.
I use master and apprentice. Always two there are, no more, no less.
Why isn’t there a journeyman Sith though?
So that’s why Sith were considered evil
I think will actually start using this “master” and “apprentice” now. Love it lol
Treat branches like Chinese dynasties. The mainline branch is the one having the mandate of heaven.
And they tend to fracture and rejoin seemingly at random, but with certain regularity
I’m… I’m not sure that’s the flex you think it is.
I think it’s mostly a shitpost lol
You’re not wrong.
I’ve started converting my ‘master’ branches to ‘main’, due to the fact that my muscle-memory has decided that ‘main’ is the standard name. And I don’t have strong feelings either was
I think ‘master’ is fine for the master branch. It’s a master copy of the codebase.
I think ‘main’ is fine for the main branch. It’s the main branch of the repo.
I use ‘main’ at work cos that’s what my git client defaults to. I use ‘master’ at home because that’s what my git client defaults to. 🤷♂️
… Has anyone adopted a ‘Master’ - ‘Padawan’ paradigm?
Imagine the mess in a thousand people project where all branches are “equal”
git config --global init.defaultBranch maini just call my main git branches trunk
