What is the purpose of "trunk-based development" with short-lived feature branches, and what practice typically must accompany it to be effective?
Correct! Well done.
Incorrect.
The correct answer is A) Trunk-based development means integrating small, frequent changes into a shared main branch rather than maintaining long-lived feature branches; to be effective it typically requires a robust automated testing and CI pipeline to catch issues quickly
Correct Answer
Trunk-based development means integrating small, frequent changes into a shared main branch rather than maintaining long-lived feature branches; to be effective it typically requires a robust automated testing and CI pipeline to catch issues quickly
Because trunk-based development relies on frequent integration of small changes, strong CI practices (fast automated tests, feature flags for incomplete work) are essential to maintain a working main branch and quickly catch any regressions introduced by the constant stream of changes.