Post #1327915
2026-02-17 21:27 UTC
It's an atrocious, pointlessly complicated system resulting in convoluted project histories prone to confusion.
[Trunk-based development with sensible tags of releases & hotfixes][oneflow] achieves the same thing without the junk complexity.
Git flow isn't overkill, it's just ill-conceived.
[oneflow]: https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow
Replies (1)
-
@thesmokingman@programming.dev 2026-02-18 01:18
This is a joke, right? OneFlow isn’t trunk-based development and [is actually gitflow with different steps](https://www.endoflineblog.com/oneflow-a-git-branching-model-and-workflow#variation-develop-master). I have yet to see any org actually use [trunk-based development](https://trunkbaseddevelopment.com/) mostly because I’ve not seen [cherry-picking from the trunk](https://trunkbaseddevelopment.com/branch-for-release/) adopted at any large scale.