Defending "GitFlow"I've noticed a trend of defending what is mistakenly believed to be GitFlow.
I’ve noticed a trend recently in several online conversations: People defending what they believe is “GitFlow”, only to discover they don’t necissarily understand what GitFlow even is.
A choice quote:
It’s a common misconception that GitFlow requires long-lived branches. It doesn’t.
Actually, it does. It’s part of the definition of GitFlow, that you have at least two permanent branches:
In another case, it turned out the supposed GitFlow defender was actually defending a git tool, which it turns out can be used without actually using the GitFlow process.
But the strongest defense I’ve heard of GitFlow is essentially, “the team isn’t ready for something else yet.” And in my opinion, that’s not a very strong argument, either.
In virtually all cases, there’s a simpler branching model, that’s less error-prone.
Who cares if we use GitFlow?
GitFlow vs Trunk-Based Development is like Coke vs. Pepsi, right? Not really.
Implementing Continuous Delivery in Reverse - ATVIE22
If you heard about Continuous Delivery you might find it sounds great, but you are not ready for it because [insert excuse here].
Improve your software delivery