Skip to content
BENIBIX Learn

Trunk-Based Development

Development🔀 Version ControlTeam Workflows

Also known as Trunk-Based, TBD, Trunk Development

Everyone merges small changes into one main branch. They do it at least once a day.

Think of it like

Think of it like a team writing one story. Each person adds a line or two a day, so it stays one story.

Example

Jack's team merges a dozen small changes into main each day. Each one is tested, so main is always ready to ship.

Why it matters

Small daily merges mean tiny conflicts. That is what lets a team ship every day.

Definition

Trunk-based development is a strategy where everyone works on one main branch, called the trunk. Branches, if used, are tiny and short. The usual rule is to merge to the trunk at least once every 24 hours. Half-done features hide behind feature flags. Tests run on every merge to keep the trunk working.
Trunk-based: tiny branches that rejoin main within a day.

Common mistake

Merging daily without good tests. A broken trunk then breaks everyone at once.

Key takeaways

  1. 1
    One trunk. Everyone shares one main branch.
  2. 2
    Merge daily. At least once every 24 hours.
  3. 3
    Flags hide work. Unfinished features stay switched off.

Learn it properly