3 ms·
Most of the advice is on point, except for the first one: "Avoid feature branches" I think this is mistaking cause and effect. The problem is having long lived
by ricardobeat 4y ago
Most of the advice is on point, except for the first one: "Avoid feature branches"
I think this is mistaking cause and effect. The problem is having long lived branches, not the fact you have a branch.
IMO the best advice is to avoid long-running branches. This is easy to achieve by slicing features into smaller units, and using feature flags, both recommendations already featured in the list.
- gocartStatue 4y agoI have a friend that says "I'm not doing branches". He actually does branches, but they never live longer than say 2 hours. Maybe that's a confusing wording, but for people used to weeks or months-long feature branches, short-lived can still be unclear. The clearest helper "rule" for a team I came up with, was "at the end of the day, there is no branch in a repository except main". Takes time to get there, but simplifies a lot.