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.
To be completely fair, I’ve worked in places that treat Git like it’s an over-engineered SVN and use the SVN workflow, fighting against the current the entire way. “trunk” would be just fine with that crowd.
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.
To be completely fair, I’ve worked in places that treat Git like it’s an over-engineered SVN and use the SVN workflow, fighting against the current the entire way. “trunk” would be just fine with that crowd.