GitHub Flow
ELI5 — The Vibe Check
GitHub Flow is Git Flow's chill younger sibling. One rule: main is always deployable. Branch off main, do work, open a PR, merge to main, deploy. That's it. No develop branch, no release branches. Simple, fast, and perfect for teams that deploy often.
Real Talk
GitHub Flow is a lightweight branching model: main is always production-ready, features are developed on branches, changes are proposed via pull requests with review, and merging to main triggers deployment. Designed for continuous deployment environments.
When You'll Hear This
"GitHub Flow: branch, PR, merge, deploy. That's the whole process." / "We deploy 10 times a day with GitHub Flow — it's simple and it works."
Related Terms
Continuous Deployment
Continuous Deployment is like Continuous Delivery but with no one at the door — the pizza delivers itself the moment it's ready.
Feature Branches
Feature Branches mean you create a new branch for every feature, bug fix, or experiment. Work in isolation, make a PR when ready, merge when approved.
Git Flow
Git Flow is a branching model with specific branches for features, releases, hotfixes, and development. It's like a highway system with designated lanes.
Trunk-Based Development
Instead of giant feature branches that live for 3 weeks and cause merge hell, trunk-based development has everyone commit to main every day.