Atlas › 17 Git & Version Control › Branching Strategies☰ Read as one page
Branching Strategies
1.1Why Branching Strategy Matters for QAThe branching strategy your team uses determines how you manage test branches, when you run which tests, and how releases map to test…1.2The Three Main Strategies1.3GitFlow in DetailGitFlow uses two long-lived branches (main and develop) plus short-lived branches for features, releases, and hotfixes.1.4GitHub Flow in DetailGitHub Flow uses a single main branch. All work happens on feature branches that merge via pull requests.1.5Trunk-Based Development in DetailTrunk-based development takes GitHub Flow to its extreme. Feature branches live less than a day. Developers commit to main frequently…1.6Adapting Your Test Plan to the Strategy1.7Transitioning Between StrategiesTeams often start with GitFlow and migrate toward GitHub Flow or trunk-based development as their automation matures. If your team is…1.8Hands-On Exercise1. Identify which branching strategy your current team uses. 2. Map out when each type of test runs in your workflow. Are there gaps? 3. If…