Git Branching Strategies

Status: draft · Confidence: low (0.43) · Basis: verified_sources

Quality notes: broken_atomic_fact, generic_source_homepage, no_verified_sources, partial_source_verification

## TL;DR

Git branching strategies organize parallel development. Git Flow (Driessen, 2010): main + develop + feature/release/hotfix branches — thorough but complex. GitHub Flow: main + feature branches, deploy from main — simple, CI/CD-friendly. GitLab Flow: adds environment branches (staging, production). Trunk-Based Development: everyone commits to main, short-lived branches.

## Core Explanation

Git Flow: feature branches from develop, release branches for stabilization, hotfixes from main. GitHub Flow: anything in main is deployable. Trunk-Based: feature flags control release, no long-lived branches — Google and Facebook use this. Choose based on team size and release cadence: small team + continuous deploy = GitHub Flow; enterprise + versioned releases = Git Flow.

## Further Reading

- [A successful Git branching model (Vincent Driessen, 2010)](undefined)

## Related Articles

- [Multi-Agent Reinforcement Learning: Cooperation, Competition, and Emergent Strategies](../../ai/multi-agent-reinforcement-learning.md)
- [Git: Distributed Version Control Internals and Workflows](../git-distributed-version-control-internals-and-workflows.md)
- [Git Version Control System](../git.md)