Branching Strategies (Git Flow, Trunk-Based)

Summary

Different team conventions for organizing branches — Git Flow uses long-lived feature/release branches, trunk-based development favors short-lived branches merged frequently into a single main branch.

• 1Compare Git Flow and trunk-based development for a hypothetical team's release cadence.
• 2Learn why trunk-based development pairs naturally with strong CI/CD practices (Phase 6).
• 3Understand there's no single 'correct' strategy — it depends on team size and release frequency.