A successful Git branching model (2010)
I&#x27;ve got a much nicer branching model- try not to have one. Everyone works off master, and you aren&#x27;t allowed to check in code that won&#x27;t run in production. Hide unfinished features behind feature flags, and never merge&#x2F;push a change that won&#x27;t pass tests&#x2F;CI.<p>The chaos of huge feature merges (a key source of bugs I&#x27;ve experienced) is minimized. You deploy fixes hourly, not weekly (or later monthly when it just won&#x27;t seem to pass CI). The time between code being written and a bug being seen can be reduced to minutes and hours, making finding the root cause a breeze.<p>Just my preference, but very open to debate.