Trunk-based development integrates changes directly into the main code branch instead of keeping each coder on a long-lived branch. It makes coding and validation closely connected, but only works when the team protects production with disciplined practices. section 5.6
Releasing a feature safely
A coder pushes a feature to the main branch. A feature flag sends most users to the old behavior while the coder and quality assurance team test the new one. After validation, the old code is removed and everyone receives the feature. section 5.6
A workable setup depends on several safeguards:
- Push updates directly to the main branch, or use short-lived feature branches rather than maintaining separate long-term branches. section 5.6
- Use feature flags to separate deploying code from exposing a feature to every user. section 5.6
- Fill the deployment pipeline with automated tests so frequent integration does not routinely break production. section 5.6
The tradeoff is clear: peer review no longer forms the main gate before merging, so testing, controlled exposure, and continuous delivery carry more responsibility. The goal is reliable software, not merely faster code production. section 5.6 section 5.12
