Our reading notes

A Successful Git Branching Model

The original Gitflow explanation, including the author’s later advice to prefer a simpler workflow for continuously delivered applications.

What to look for

  1. 01

    Read the 2020 reflection before the original branching diagram.

  2. 02

    Distinguish software with supported versions in the field from continuously delivered web services.

Keep in mind

Originally published in 2010. The author explicitly warns against treating Gitflow as a universal standard.

Put it to work

Try this next

List which supported release versions require your current branches and remove any branch whose purpose no longer exists.

Get the planning & delivery template

Notes and exercises by Awesome CTO. The original work belongs to Vincent Driessen.

Work through the bigger question.

Our planning & delivery guide connects the reading to a practical approach and a template.

Open guide
Esc

Type to search every entry. ↑↓ to move, Enter to open.