In this post I present a Git branching strategy for developing and releasing software as I’ve used it in many of my projects, and which has turned out to be very successful.

Saurav Jain

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post presents a successful Git branching model for software development projects. It discusses the main branches, supporting branches (feature, release, and hotfix branches), and the recommended workflow. The post emphasizes the importance of considering contextual factors when choosing a branching strategy.

A successful Git branching model

<p>Please read the authors note in the article on how this branching mechanism doesn’t fit on continuously delivered. This approach is not a one-size-fits-all</p>


<p>The best article on git naming conventions and git flow</p>
