I'm curious if anyone is still using git-flow? It seems like the entire industry just unanimously (although quietly) agreed that it was a bad idea and abandoned it.
There is huge array of alternatives between git-flow and trunk based development.
Most still miss on benefits TBD and CI bring.
Companies settle in the middle because git-flow is very specialized branching strategy. You almost need physically sold software (but that's still not enough!).
10 comments
[ 4.5 ms ] story [ 27.5 ms ] threadI'm curious if anyone is still using git-flow? It seems like the entire industry just unanimously (although quietly) agreed that it was a bad idea and abandoned it.
Lots of incentives towards longer lived feature branches
Anytime I've worked on long lived branches chaos is doomed to ensue.
Most still miss on benefits TBD and CI bring.
Companies settle in the middle because git-flow is very specialized branching strategy. You almost need physically sold software (but that's still not enough!).