A successful Git branching model » nvie.com
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.
Vincent Driessen • January 5, 2010 Note of reflection · March 5, 2020 ¶ This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being. In those 10 years, git-flow (the branching model laid out in this article) has become hugely popular in many a software team to the point where people have started treating it like a standard of sorts — but unfortunately also as a dogma or panacea. During those 10 years, Git itself has taken the world by a storm, and the most popular type of software that is being developed with Git is shifting mo
saved by
related reading
- Learn how Git fits into an agile workflow | Atlassianatlassian.com
- How Git works: A complete guide to branches, merges, and collaborationdeveloper.ibm.com
- Git at any scalecursor.com
- Useful git commands for SRE and DevOps engineersreliabilityengineering.substack.com
- Trunk-based Development | Atlassianatlassian.com
- Git - user-manual Documentationgit-scm.com
- Using Gitcs61bl.org
- Conventional Commitsconventionalcommits.org
- Merging vs. Rebasing | Atlassian Git Tutorialatlassian.com
- Git from the Bottom Upjwiegley.github.io
- How I Use Git Worktreesmatklad.github.io
- Git Can't Be Made Consistent: bramcohen — LiveJournalbramcohen.livejournal.com