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.