Summary - Branch protection

Combine protection rules to secure the main branch.

Combining Branch Protection Rules

A reliable main branch protection setup is created by applying multiple rules together. Requiring pull requests restricts direct changes; the review policy requires team approval; and status checks require automated tests to succeed. Together, these rules make it harder for faulty or unreviewed changes to reach the main branch.

main:
  require_pull_request: true
  required_approvals: 2
  required_status_checks:
    contexts:
      - test

Each rule provides a different layer of protection in the development process.

Exercise Protect the Main Branch with Multiple Rules

Complete the protection settings for the main branch. Enable required pull requests, require at least two approvals, and set strict: true under required_status_checks. Finally, add the test check to the contexts list.

Show example solution

main:
  require_pull_request: true
  required_approvals: 2
  required_status_checks:
    strict: true
    contexts:
      - test

Test yourself

Which two rules should be combined when both team approval and successful automated tests are required before a change reaches the main branch?
- Commit message and repository description
- Stash and file history
- Required review and required status checks
- Branch deletion and tag creation
Show answer

Required review and required status checks — Required reviews provide team approval, while required status checks ensure that automated checks succeed.

Set the Approval Count for the Main Branch

main:
  require_pull_request: true
  ____: 2

Show answer

main:
  require_pull_request: true
  required_approvals: 2

Protection Layers

Pull request zorunluluğu

Routes changes through review
Required review

Requires team approval
Status check

Validates automated tests
Dal koruma politikası

Enforces rules together

Next lesson: Rebase

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies