Your team is adopting a continuous integration model where developers commit to the main branch multiple times a day. Long-lived feature branches are banned. Features that are incomplete are hidden behind toggles. Which branching strategy are you implementing?

Question

Sunny · Accepted Answer

Trunk-based development. Trunk-based development dictates that all developers integrate their changes directly into a shared trunk (main branch) frequently (at least daily). It avoids merge conflicts associated with long-lived feature branches. Incomplete features are managed using feature flags. GitFlow relies heavily on multiple long-lived branches (develop, release, master).

Your team is adopting a continuous integration model where developers commit to the main branch multiple times a day. Long-lived feature branches are banned. Features that are incomplete are hidden behind toggles. Which branching strategy are you implementing?

Your team is adopting a continuous integration model where developers commit to the main branch multiple times a day. Long-lived feature branches are banned. Features that are incomplete are hidden behind toggles. Which branching strategy are you implementing?

📚 What This Question Tests