Trunk-based development
Also called: TBD
Last updated:
Trunk-based development is a source-control practice in which developers integrate to one shared branch — the trunk, often main — in small, frequent commits, rather than working on long-lived feature branches that merge weeks later. The trunk is kept releasable at all times, which is what makes continuous integration and continuous delivery practical.
Why trunk-based development needs feature flags
The relationship to CI/CD
Want the full picture? Read the concept guide: What are feature flags? →
Related terms
Feature flag
A feature flag is a conditional in your code whose value is controlled from a remote dashboard, letting you turn functionality on or off without deploying new code.
Dark launch
A dark launch ships a feature to production turned off or invisible to users, so the code runs in the live environment before anyone sees it — you reveal it later on your own schedule.
Progressive delivery
Progressive delivery is the practice of releasing software gradually and reversibly — using feature flags, canary releases, and percentage rollouts to expand exposure step by step while watching metrics, instead of shipping to everyone at once.
Try it in your own app
Free Solo plan covers 10 flags and 2 environments. No credit card, no demo call — sign up and ship.