3 ms·
Seeing as the advice is given to work in feature branches, I think the target audience is those who just started working with git? Or on a bigger project, with
by dstick 6y ago
Seeing as the advice is given to work in feature branches, I think the target audience is those who just started working with git? Or on a bigger project, with other people?
The only time I'd maybe work without feature branches is on a solo project that hasn't been launched yet. But even then, probably for a quick prototype. As soon as there's a publicly deployed master, it's feature branches each and every time. Too much can go wrong ;-)
- martin_drapeau 6y agoI led a team of 20 devs using this approach. It worked very well. No one stepped on each other's toes. The advantages noted in the article are so true. Avoiding feature branches was a game changer for us. Move faster with much less stress.
- marcosdumay 6y agoThe important problems to solve are all social: how do you divide the work, how people talk to each other when working on the same code, etc. If you solve those right, your team can be successful with any git workflow, and if you solve those wrong, they will fail despite any git workflow. After you get the important things right, the will exist relevant optimizations on the workflow like those on the article. But they won't make or break your team, and will certainly depend on a lot of details so any universal preaching must be taken with care.