CodeBlanks Logo Icon CodeBlanks
Login Register

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.

Practice 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.

Starter code

terminal
# Pull request zorunluluğu
# İnceleme onay sayısı
# Otomatik kontroller

Sample solution

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

Expected output

Ana dal için tüm koruma kuralları etkinleştirildi.

Questions and answers

Review the lesson questions together with their answers. To test yourself, solve the lesson interactively.

1 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 Correct answer
  • Branch deletion and tag creation

Explanation: Required reviews provide team approval, while required status checks ensure that automated checks succeed.

2 Set the Approval Count for the Main Branch

Question 
main:
  require_pull_request: true
  ____: 2
Answer 
main:
  require_pull_request: true
  required_approvals: 2

Explanation: When <code>required_approvals</code> is set to 2, at least two approvals are required before merging.

3 Protection Layers

Term Meaning
Pull request zorunluluğu Routes changes through review
Required review Requires team approval
Status check Validates automated tests
Dal koruma politikası Enforces rules together

All lessons in Advanced

1 Interactive rebase

  1. rebase -i
  2. pick reword squash
  3. edit drop
  4. Summary - Interactive rebase

2 Bisect

  1. git bisect
  2. good and bad
  3. Automatic bisect
  4. Summary - Bisect

3 Blame

  1. git blame
  2. Line history
  3. blame -L
  4. Summary - Blame

4 Submodule

  1. What is a submodule?
  2. submodule add
  3. submodule update
  4. Summary - Submodule

5 Worktree

  1. git worktree
  2. worktree add
  3. worktree list
  4. Summary - Worktree

6 Hooks

  1. What is a hook?
  2. pre-commit
  3. commit-msg
  4. Summary - Hooks

7 Advanced log

  1. --graph
  2. --format
  3. --since --until
  4. Summary - Advanced log

8 Archive

  1. git archive
  2. zip and tar
  3. Specific branch
  4. Summary - Archive

9 Advanced stash

  1. stash -u
  2. stash branch
  3. stash show -p
  4. Summary - Advanced stash

10 Advanced cherry-pick

  1. cherry-pick -n
  2. cherry-pick range
  3. cherry-pick strategy
  4. Summary - Advanced cherry-pick

11 Actions workflow

  1. matrix
  2. cache
  3. secrets
  4. Summary - Actions workflow

12 GitHub Pages

  1. What is Pages?
  2. Branch publish
  3. Custom domain
  4. Summary - GitHub Pages

13 Branch protection

  1. Protected branch
  2. Required review
  3. Status check
  4. Summary - Branch protection

14 Advanced final

  1. Rebase
  2. Bisect
  3. Submodule
  4. Hook