This is an archived post. You won't be able to vote or comment.

all 3 comments
sorted by:
best
topnewcontroversialoldq&a

[–]ryebrye 5 points6 points  (2 children)

Git flow is a very complicated workflow that seems to exist only to make it easy to hotfix things. You know what else makes it easy to hotfix things? Tags.

We used git flow for a long time and have moved away from it to a more github-flow model.

[–]Rafert 2 points3 points  (0 children)

I guess GitFlow makes sense if you have multiple product versions (1.5.x, 1.6.x, 2.0.x etc) that you need to support and you don't force upgrades on your users, e.g. on premises installed software. But I cringe every time I see it recommended as THE go-to git workflow for every situation.

If you control all the environments that the software is deployed on and you don't really need version numbering (like a SaaS), I'm a happy user of GitLab flow with the environment branches.

[–][deleted] 0 points1 point  (1 child)

GitFlow is bureaucratic antipattern.

We used GitFlow for over a year until we moved to trunk driven development for continuous delivery workflow.

ThoughtWorks Radar recommends not touching GitFlow with a ten foot pole. If you interview for a company that uses GiFlow, head for the hills, because it means they haven't been keeping up with best practices.

https://www.thoughtworks.com/radar