4 ms·
Leaning into the tree metaphor (and following the precedent of other version control systems), git should have used the term trunk instead of master or main.
by cpeterso 3y ago
Leaning into the tree metaphor (and following the precedent of other version control systems), git should have used the term trunk instead of master or main.
- hnarn 3y agoWhy? That would heavily imply that master/main is somehow technically different from all other branches (since a trunk is certainly not a branch), which to my knowledge is not true.
- cpeterso 3y agoI see what you mean, but don't "master" and "main" also imply some special authority? Trunk-based development with branches forking off and merging back into the trunk (a DAG, unlike a real tree! :) is an extremely common workflow. https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/
- Kuraj 3y agoBy following this metaphor, a trunk would be the original commit, whereas branches are the tree branch tips.
- galaxyLogic 3y agoAnd consider that because every folder can have its own .git subfolder, we can have several paralle trunks/repositories at the same time, meaning we have a forest. I haven't really seen specific guidelines as to when and why should anyone start a new repo. Are there some? Or is "mono-repo" the best solution, and when and for whom. Surely we need more than one git-repo in the whole world?!