Branch Protection
Branch protection rules help you enforce code quality and prevent accidental deletions of important branches (like main).
Configuring Rules
Section titled “Configuring Rules”- Navigate to your repository.
- Click Settings > Branches.
- Click Add Rule.
Rule Options
Section titled “Rule Options”Branch Pattern
Section titled “Branch Pattern”Specify which branches this rule applies to.
main: Matches exactly the main branch.release/*: Matchesrelease/v1,release/v2, etc.*: Matches all branches (use with caution).
Require Pull Request
Section titled “Require Pull Request”Ensures that no one can push directly to the branch. All changes must go through a Pull Request.
Require Approvals
Section titled “Require Approvals”Set the minimum number of code reviews required before merging.
- Recommended: 1 or 2.
Dismiss Stale Reviews
Section titled “Dismiss Stale Reviews”If checked, pushing new commits to a PR will dismiss existing approvals. This ensures reviewers see the latest code before merging.
Require Status Checks (CI)
Section titled “Require Status Checks (CI)”(Coming Soon) Require CI/CD jobs (GitHub Actions) to pass before merging.
Bypassing Protection
Section titled “Bypassing Protection”Repository administrators can bypass protection rules if “Include Administrators” is not checked. Use this Power cautiously!