Branch protection rules in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are branch protection rules in Git?

Branch protection rules are settings that prevent certain actions on important branches, like deleting or force-pushing, to keep the code safe and stable.

beginner

Name one common restriction set by branch protection rules.

One common restriction is requiring pull request reviews before merging changes into the protected branch.

beginner

Why is it important to protect the main branch in a repository?

Protecting the main branch helps avoid accidental changes or deletions that could break the project or lose important work.

intermediate

How do branch protection rules improve team collaboration?

They enforce code reviews and tests before merging, ensuring everyone agrees on changes and the code stays reliable.

intermediate

Can branch protection rules prevent force pushes? Explain.

Yes, branch protection rules can block force pushes to avoid overwriting history and losing work.

What does a branch protection rule typically prevent?

A Direct pushes to the protected branch

B Creating new branches

C Cloning the repository

D Deleting the repository

Branch protection rules often prevent direct pushes to ensure changes go through reviews.

Which of these is a common requirement in branch protection rules?

A Automatically delete branches after merge

B Require pull request reviews before merging

C Disable all commits

D Allow force pushes anytime

Requiring pull request reviews helps maintain code quality.

What happens if you try to force push to a protected branch?

A The branch is deleted

B The push succeeds without warning

C The push is blocked

D The repository is locked

Branch protection rules block force pushes to protect branch history.

Why protect the main branch in a Git repository?

A To prevent accidental changes that could break the project

B To stop users from cloning the repo

C To disable all commits permanently

D To allow anyone to push freely

Protecting main keeps the project stable and safe from mistakes.

Which action is NOT controlled by branch protection rules?

A Force pushing

B Merging pull requests

C Pushing commits directly

D Deleting the repository

Branch protection rules do not control repository deletion.

Explain what branch protection rules are and why they are important in Git.

Think about how to keep important branches safe and stable.

Describe how branch protection rules help teams work better together.

Consider teamwork and quality control.

Practice

1. What is the main purpose of branch protection rules in Git repositories?

easy

A. To prevent direct changes to important branches without review or checks

B. To delete branches automatically after merging

C. To speed up the cloning process of the repository

D. To allow anyone to push changes without restrictions

Solution

1. Step 1: Understand branch protection rules

   Branch protection rules are designed to keep important branches safe by enforcing rules like requiring reviews or passing tests before changes can be merged.

2. Step 2: Identify the correct purpose

   Options A, B, and D describe unrelated or incorrect behaviors. Only To prevent direct changes to important branches without review or checks correctly describes the purpose of branch protection rules.

3. Final Answer:

   To prevent direct changes to important branches without review or checks -> Option A

4. Quick Check:

   Branch protection = prevent unsafe direct changes [OK]

Hint: Branch protection means safe branches, no direct unsafe changes [OK]

Common Mistakes:

• Thinking branch protection deletes branches
• Confusing branch protection with performance features
• Assuming branch protection allows unrestricted pushes

2. Which of the following is the correct way to enable branch protection for the main branch on GitHub via the web interface?

easy

A. Create a file named branch-protect.yml in the root directory

B. Run git protect main in the terminal

C. Go to Settings > Branches > Add rule > Specify 'main' > Select protections > Save

D. Push a branch named protected/main to enable protection

Solution

1. Step 1: Know how to set branch protection on GitHub

   Branch protection rules are set in the repository's Settings under Branches by adding a rule for the branch name and selecting protections.

2. Step 2: Evaluate options

   Go to Settings > Branches > Add rule > Specify 'main' > Select protections > Save describes the correct web interface steps. Options B, C, and D are invalid commands or methods not supported by GitHub.

3. Final Answer:

   Go to Settings > Branches > Add rule > Specify 'main' > Select protections > Save -> Option C

4. Quick Check:

   GitHub branch protection set via Settings > Branches [OK]

Hint: Branch protection is set in repo Settings under Branches [OK]

Common Mistakes:

• Trying to use git CLI commands that don't exist
• Assuming config files control branch protection
• Thinking branch protection is automatic on branch creation

3. Given this branch protection rule requiring pull request reviews before merging, what happens if a user tries to push directly to the protected branch?

Rule: Require pull request reviews before merging

medium

A. The push is rejected with an error message

B. The push succeeds without any checks

C. The branch is automatically deleted

D. The push creates a new branch instead

Solution

1. Step 1: Understand the rule effect

   Requiring pull request reviews means direct pushes to the branch are blocked to enforce code review before changes.

2. Step 2: Predict the push behavior

   Because direct pushes are blocked, the push attempt will be rejected with an error message. Options A, B, and C are incorrect behaviors.

3. Final Answer:

   The push is rejected with an error message -> Option A

4. Quick Check:

   Require review blocks direct push = push rejected [OK]

Hint: Require review means no direct push allowed [OK]

Common Mistakes:

• Assuming push silently creates new branch
• Thinking push succeeds without review
• Believing branch gets deleted on push

4. A developer sets a branch protection rule to require status checks before merging, but merges are still allowed without passing checks. What is the likely cause?

medium

A. The developer forgot to push the branch

B. The status checks are not selected/enabled in the branch protection settings

C. The repository has no branches

D. The branch protection rules only apply to forks

Solution

1. Step 1: Analyze the protection rule setup

   Requiring status checks means you must select which checks must pass in the branch protection settings.

2. Step 2: Identify why merges bypass checks

   If merges happen without passing checks, it usually means the required checks were not properly selected or enabled in the settings.

3. Final Answer:

   The status checks are not selected/enabled in the branch protection settings -> Option B

4. Quick Check:

   Missing selected checks = merges bypass checks [OK]

Hint: Enable and select status checks in protection settings [OK]

Common Mistakes:

• Assuming branch protection applies only to forks
• Thinking pushing branch affects protection
• Ignoring the need to select specific status checks

5. You want to protect the release branch so that only team leads can push directly, and everyone else must use pull requests with reviews. Which branch protection settings should you apply?

hard

A. Require status checks but allow anyone to push directly

B. Enable 'Require signed commits' only

C. Disable all protections and trust the team

D. Enable 'Restrict who can push' to team leads and require pull request reviews for others

Solution

1. Step 1: Understand the requirement

   The goal is to allow only team leads to push directly and force others to use pull requests with reviews.

2. Step 2: Choose correct settings

   Enabling 'Restrict who can push' to team leads limits direct pushes to them. Requiring pull request reviews ensures others must use PRs. Options B, C, and D do not meet both conditions.

3. Final Answer:

   Enable 'Restrict who can push' to team leads and require pull request reviews for others -> Option D

4. Quick Check:

   Restrict push + require reviews = controlled direct push [OK]

Hint: Restrict push to leads + require reviews for others [OK]

Common Mistakes:

• Only requiring signed commits without push restrictions
• Disabling protections and trusting team
• Allowing anyone to push directly with status checks only