GitHub Flow — Explained with Examples

GitHub Flow is a lightweight branching strategy where feature branches are proposed via pull requests and merged directly into main.

GitHub Flow simplifies branching to a single long-running branch (main). Developers create feature branches from main, make changes, open a pull request for review, and merge back to main after approval. The model relies on continuous deployment — anything in main is deployable. There are no develop or release branches.

Think of GitHub Flow like an assembly line with a single quality checkpoint. Each worker (developer) builds a part on their own workbench (feature branch), submits it for inspection (pull request), and if approved, it goes directly to the shipping dock (main branch). No intermediate staging areas.

GitHub Flow emerged from GitHub’s own development practice. It suits teams practicing continuous delivery, where each merge to main triggers automated testing and deployment. The simplicity reduces overhead compared to GitFlow.

# Create feature branch
git checkout -b add-payment-api main

# Commit changes
git add .
git commit -m "Add payment API endpoint"

# Push and open pull request
git push -u origin add-payment-api
# Then open a PR on GitHub.com

# After approval, merge via GitHub UI

Because there is no release branch, teams often use feature flags to hide incomplete features in production. This keeps main always deployable.

GitFlow, Trunk-Based Development, Branch, Pull Request

Trunk-Based Development