📄 Article
✓ Link checked
Free
Intermediate
A focused reference on the simplest branching model that works for small teams: short lived branches off one trunk, merged fast. It spells out the version scaled down for a couple of engineers, so you do not accidentally adopt a complex GitFlow setup built for large release trains. Use it to pick a branching rule you can write in one sentence.
Trunk Based Development
From trunkbaseddevelopment.com by Paul Hammant Reference site
- Keep branches short lived and merge them within a day or two
- One trunk that stays releasable beats many long running branches
- Small teams can commit to trunk directly or via quick pull requests
