And why your group may be suffering from Stockholm syndrome with their branching method
Keep in mind the last time you confidently said “let’s make use of Gitflow” in a meeting? Every person nodded approvingly, and you felt like you would certainly simply recommended using industry-standard finest methods. Well, I despise to break it to you, yet you might have just volunteered your group for an administrative problem that’s been spruced up as expert software program development.
Do not obtain me wrong– Gitflow isn’t inherently evil. Yet someplace in the process, it became the business match of branching methods: formal, impressive-looking, and totally excessive for the majority of circumstances.
The Rise of the Gitflow Empire
Back in 2010, Vincent Driessen published his popular post “A Successful Git Branching Model” and accidentally produced a beast. Gitflow became so preferred that it was taken into consideration a disruptive and unique strategy for handling Git branches, with developers relocating in between business anticipating to locate this standard process.
The trouble? Success bred dogma. What started as “right here’s something that helped us” somehow came to be “THIS IS THE METHOD” throughout the whole industry. It resembles everyone collectively chose that due to the fact that one team had success …