2 ms·
I'm pretty sure trunk-based development includes using feature branches and MRs/reviews etc. I didn't get the impression we were always supposed to commit direc
by globular-toast 1y ago
I'm pretty sure trunk-based development includes using feature branches and MRs/reviews etc. I didn't get the impression we were always supposed to commit directly to master (although that is possible for trivial things which reduces overhead).
Is everyone talking about the same thing here?
- JimDabell 1y agoThere are different flavours of TBD. Some use short-lived feature branches, some commit directly to master. See: https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/
- globular-toast 1y agoIf your team is very small then strictly creating feature branches and pressing the merge button immediately because there's nobody left to review it is silly. I like that it gracefully degenerates into just committing directly to the trunk when it makes sense. This works with git (or DVCS in general) because your local "master" or whatever is a short lived branch. People seem to forget but with git you are branching every time you clone. Obviously committing broken stuff and WIPs directly to the trunk isn't going to work.