trunk-based development
A version-control branching strategy in which all developers integrate their work into a single shared branch (the 'trunk' or 'main') frequently, keeping the branch in a releasable state.
Full Definition
Trunk-based development (TBD) contrasts with long-lived feature-branch workflows by requiring developers to commit to the main branch at least once a day, using feature flags to hide incomplete work. The approach is associated with high-performing engineering teams and is a prerequisite for many CI/CD practices. Editors should hyphenate 'trunk-based' when used as a compound modifier before a noun ('trunk-based development', 'trunk-based workflow'). The 'trunk' is synonymous with 'main' or 'master' branch in Git terminology, though 'main' is now the preferred default branch name.
Usage
Usage note: Hyphenate 'trunk-based' as a compound modifier. The abbreviation 'TBD' risks confusion with 'to be determined'; spell out in most contexts. Clarify that 'trunk' equates to 'main' in Git repositories to avoid confusion with older SVN terminology.
In Context
- "The engineering handbook mandates trunk-based development to support the team's CI/CD pipeline." — Engineering handbook
- "Unlike Gitflow, trunk-based development discourages long-lived feature branches." — Branching strategy comparison guide