- cross-posted to:
- hackernews@derp.foo
- cross-posted to:
- hackernews@derp.foo
You must log in or register to comment.
Apart from the historical value, the most important part of this article now is the “Note of reflection” added 10 years after it’s inception:
If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.
I don’t think this work flow is relevant any more even for teams that don’t do CD, to be honest. It was a messy work flow to begin with and I haven’t seen it applied successfully in practice.
As an in-depth alternative, I recommend “Patterns for Managing Source Code Branches” by Martin Fowler: https://martinfowler.com/articles/branching-patterns.html