trunk-based development

A branching practice where developers merge small changes into one main branch, the trunk, at least once a day, keeping any other branches short-lived.

In more detail

DORA's research describes it as three or fewer active branches, merging to trunk at least daily, and no code freezes. Because everyone integrates constantly, merge conflicts stay small, and it pairs with continuous integration and continuous delivery.

Related terms

Taught in

References

Certification courses