πΊοΈ Branch Flow with Pull Requests (PRs)
Let's assume your repo has these main branches:
css
main β π’ production / stable
acceptance β π‘ staging / testing
backend β π΅ backend dev
frontend β π΅ frontend dev
feature/* β π§ feature branches
documentationβ π docs-only changes
π Typical Flow (Push β PR β Merge):
plaintext
[feature/backend-login]
β
βΌ
Pull Request
β
βΌ
[backend]
β
βΌ
Pull Request
β
βΌ
[acceptance]
β
βΌ
Pull Request
β
βΌ
[main]
β Example Workflow
- Create a Feature Branch
git checkout backend
git pull origin backend
git checkout -b feature/backend-login
2. Do your work, commit and push:
git push origin feature/backend-login
- Open a Pull Request: From: feature/backend-login
Into: backend
Add reviewers, description, link to related issues.
- After Approval: Merge into backend, then repeat this upward:
PR from backend β acceptance
Test/stage in acceptance
PR from acceptance β main once stable
π Bonus: Directional Naming Diagram
plaintext
[feature/*] βββΆ [backend/frontend] βββΆ [acceptance] βββΆ [main]
β²
β
[documentation]
π Each arrow is a Pull Request (PR)
β
You only push to feature/dev branches, not main directly.
π‘ Tips
Keep main protected (require PRs + code review)
Label PRs by type: feature, fix, hotfix, docs, etc.
Automate testing in acceptance branch via CI (GitHub Actions, etc.)
Top comments (0)