Trunk Based Development
Introduction
One line summary
A source-control branching model, where developers collaborate on code in a single branch called ‘trunk’ *,
resist any pressure to create other long-lived development branches by employing documented techniques. They
therefore avoid merge hell, do not break the build, and live happily ever after.
* main for the Git community since 2020 (master with unsavory connotations before)
Shared branches off mainline/main/trunk are bad at any release cadence:
Trunk-Based Devel...
Read more at trunkbaseddevelopment.com