BR
Branch Strategy
Branch naming conventions and workflow patterns
Details
Language / Topic
_UUniversal
Category
Git Workflow
Rules
balanced
- Use descriptive branch names: `feature/`, `fix/`, `chore/`, `docs/` prefixes followed by a short slug.
- Keep branches short-lived — merge or rebase frequently to avoid drift from main.
- Use short-lived feature branches that merge within 1-3 days — long-lived branches cause merge conflicts and integration pain.
- Protect the main branch — require PR reviews and passing CI before merge.
- Delete branches after merging to keep the repository clean.
- Rebase feature branches on main before creating a PR to ensure a clean diff.