Trunk-Based CI
Trunk-based CI is a source-control and continuous-integration practice in which developers integrate small, frequent changes directly into a single shared branch (the trunk) rather than working in long-lived feature branches.
Definition
Trunk-based CI is a source-control and continuous-integration practice in which developers integrate small, frequent changes directly into a single shared branch (the trunk) rather than working in long-lived feature branches.
Overview
Trunk-based development stands in contrast to workflows built around long-lived feature branches, where developers work in isolation for days or weeks before merging, and merges become increasingly painful the longer a branch diverges from the trunk. In trunk-based CI, developers commit small, incremental changes directly to the trunk (commonly `main`) at least once a day, and every commit runs through an automated continuous integration pipeline of builds and tests before it's considered safe. Because work is integrated continuously rather than in large batches, trunk-based CI relies heavily on feature toggles to keep unfinished functionality hidden from end users while its code still merges into the trunk, and it favors short-lived branches — if branches are used at all — that live for hours rather than weeks. This approach is one of the foundational practices identified by the DevOps Research and Assessment (DORA) program as correlating with high-performing software delivery teams, since it minimizes merge conflicts, keeps the trunk always close to a releasable state, and enables true continuous integration and continuous deployment rather than integration only at the end of a release cycle. Adopting trunk-based CI usually requires supporting practices beyond just a branching policy: a fast and reliable automated test suite so that every commit can be validated quickly, feature toggles to decouple merging from releasing, and a culture of small, reviewable pull requests. Teams moving from GitFlow or long-lived feature branches to trunk-based CI often find the biggest adjustment is disciplined use of feature flags and a willingness to ship partially complete work behind a disabled toggle rather than holding it back in a branch.
Key Concepts
- Developers commit small changes directly to a single shared trunk branch frequently
- Short-lived or no feature branches, typically merged within hours rather than weeks
- Every commit triggers an automated build and test pipeline before being considered safe
- Heavy reliance on feature toggles to hide incomplete functionality from users
- Identified by DORA research as a practice correlated with elite software delivery performance
- Keeps the trunk continuously close to a releasable, deployable state
- Reduces merge conflict risk compared to long-lived branch workflows
Use Cases
Frequently Asked Questions
From the Blog
Biometrics Explained: How Body-Based Authentication Works
Biometrics are measurements of physical or behavioral traits, such as fingerprints or facial structure, used to verify identity. This guide explains how biometric systems work, common types, and the security and privacy trade-offs involved.
Read More Cloud & CybersecurityLogic Programming Language: How Rule-Based Code Works
A logic programming language lets you describe facts and rules instead of step-by-step instructions, and the system figures out how to satisfy a query. This guide explains the paradigm, inductive logic programming, and where it is still used today.
Read More AI & TechnologyCompetency-Based Training: How It Works and Why It Sticks
Competency-based training measures progress by demonstrated skill mastery instead of time spent in a classroom. This guide explains how it works, how it differs from traditional training, and how to implement it effectively.
Read More AI & TechnologyCompetency-Based vs Outcome-Based Education Explained
Competency-based education advances learners when they demonstrate mastery, while outcome-based education designs curricula around defined learning outcomes. This guide compares both models and explains where each fits best.
Read More