Reduce tangled code branches with trunk-based development
Trunk-based development reduces cycle time, speeding up the journey from code to customer.
Feature flags are a key ingredient in trunk-based development, freeing development teams to merge directly to master and avoid the complexity of long-lived feature branches.
What is trunk-based development?
Trunk-based development helps teams move faster by integrating changes continually. Merging every change to the trunk (aka main branch) means the code base is always ready to release, a core tenet of continuous delivery.
Trunk-based development avoids the “merge hell” caused by long-lived branches, where each branch can cause merge conflicts and additional QA time.
Trunk-based development case studies
Get the O’Reilly eBook
Adopting trunk-based development with feature flags
Feature flags are a requirement to succeed at trunk-based development in larger teams. The only way to ensure that a shared branch is always releasable is to hide unfinished features behind flags that are turned off by default.
Developers can build a new feature by turning the flag off and deploying to master at any time, preventing merge conflicts before a new feature is completed.
Split makes trunk-based development seamless with feature flags to keep code dormant and built-in alerting to warn you when newly released code should be turned off.
Eliminate your feature branches
Feature flags free you to merge immediately without the worry of code dependencies and team coordination.