Does anybody actually use trunk based development in their company?
https://programming.dev/post/14119313

Does anybody actually use trunk based development in their company? - programming.dev
I’ve heard it thrown around in professional circles and how everybody’s doing it
wrong, so… who actually does use it? For smaller teams
[https://trunkbaseddevelopment.com/trunk1b.png] “scaled” trunk based development
[https://trunkbaseddevelopment.com/trunk1c.png]
I’ve been a fan of git-flow for a long time. It makes the master consistently stable and production ready, gives mechanisms for hotfixing, patching, releasing, tagging, and regular feature dev with a running develop branch. This tends to be more stable than Wild West commits into dev direct, since you work on a feature in isolation, and then merge the feature in when it’s ready, and keeps prod in its own lane so there’s no risk of a feature accidentally nuking something.