Sibshops@lemmy.myserv.one to Programmer Humor@programming.dev · 8 days agoMaster vs main (again)lemmy.myserv.oneimagemessage-square46fedilinkarrow-up1328arrow-down136
arrow-up1292arrow-down1imageMaster vs main (again)lemmy.myserv.oneSibshops@lemmy.myserv.one to Programmer Humor@programming.dev · 8 days agomessage-square46fedilink
minus-squareSibshops@lemmy.myserv.oneOPlinkfedilinkarrow-up3·7 days agoCause git doesn’t work that way. There is no trunk. It’s all branches.
minus-squareBatmanAoD@programming.devlinkfedilinkarrow-up2·7 days agoBut 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.
minus-squareRicky Rigatoni@retrolemmy.comlinkfedilinkarrow-up7·7 days agoWhat is a trunk if not a large branch
minus-squareSibshops@lemmy.myserv.oneOPlinkfedilinkarrow-up5·edit-27 days agoOh, 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.
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.