Required status checks in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are required status checks in GitHub?

Required status checks are automated tests or validations that must pass before a pull request can be merged. They help ensure code quality and prevent broken code from entering the main branch.

beginner

How do required status checks improve collaboration in a team?

They enforce that all code changes pass tests and checks before merging, reducing bugs and conflicts. This keeps the main branch stable and trustworthy for everyone.

beginner

Name two common types of status checks used as required checks.

1. Continuous Integration (CI) build tests
2. Code quality or linting checks

beginner

What happens if a required status check fails on a pull request?

The pull request cannot be merged until the failing check is fixed and passes. This prevents potentially harmful code from being added.

beginner

Where can you configure required status checks in GitHub?

In the repository settings under Branch Protection Rules, you can select which status checks must pass before merging.

What is the main purpose of required status checks in GitHub?

A To ensure automated tests pass before merging

B To allow anyone to merge without review

C To delete branches automatically

D To create new repositories

Required status checks ensure automated tests or validations pass before merging code.

Where do you set required status checks in a GitHub repository?

A GitHub Actions workflow file

B Issues tab

C Pull request comments

D Branch Protection Rules in repository settings

Required status checks are configured in Branch Protection Rules under repository settings.

If a required status check fails, what happens to the pull request?

A It deletes the branch

B It cannot be merged until the check passes

C It merges automatically

D It closes the pull request

Pull requests with failing required status checks cannot be merged until fixed.

Which of these is NOT a typical required status check?

A Code linting

B Continuous Integration build

C Manual code review approval

D Automated tests

Manual code review is separate from automated status checks.

Why are required status checks important for the main branch?

A They keep the main branch stable and reliable

B They speed up merging without tests

C They allow anyone to push directly

D They delete old branches automatically

Required status checks help keep the main branch stable by preventing broken code merges.

Explain what required status checks are and why they matter in a Git workflow.

Think about how automated tests help keep code safe before merging.

Describe how to set up required status checks in a GitHub repository.

Look in the settings area where you protect branches.

Practice

1.

What is the main purpose of required status checks in GitHub branch protection?

easy

A. To automatically delete branches after merging

B. To prevent merging if tests or checks fail

C. To allow anyone to push directly to the branch

D. To create new branches automatically

Solution

1. Step 1: Understand what required status checks do

   They stop merging pull requests if tests or checks fail, ensuring code quality.

2. Step 2: Identify the main goal in branch protection

   The goal is to keep the main branch stable by blocking merges that fail checks.

3. Final Answer:

   To prevent merging if tests or checks fail -> Option B

4. Quick Check:

   Required status checks = prevent bad merges [OK]

Hint: Required status checks block merges if tests fail [OK]

Common Mistakes:

• Thinking they delete branches automatically
• Believing they allow direct pushes without review
• Confusing with branch creation features

2.

Which of the following is the correct way to enable required status checks in GitHub?

Settings > Branches > Branch protection rules > Add rule > Require status checks to pass before merging

easy

A. Settings > Security > Enable required checks

B. Settings > Actions > Workflows > Enable status checks

C. Settings > Branches > Branch protection rules > Add rule > Require status checks to pass before merging

D. Settings > Pull requests > Require reviews

Solution

1. Step 1: Locate where branch protection rules are set

   Branch protection rules are found under Settings > Branches in GitHub repository.

2. Step 2: Identify the correct path to enable required status checks

   Within branch protection rules, you add a rule and select 'Require status checks to pass before merging'.

3. Final Answer:

   Settings > Branches > Branch protection rules > Add rule > Require status checks to pass before merging -> Option C

4. Quick Check:

   Enable checks via branch protection rules [OK]

Hint: Enable checks in branch protection rules settings [OK]

Common Mistakes:

• Looking under Actions or Security instead of Branches
• Confusing status checks with pull request reviews
• Selecting unrelated settings paths

3.

Given a branch protection rule with required status checks enabled for ci/test and ci/lint, what happens if a pull request has ci/test passing but ci/lint failing?

medium

A. The pull request can be merged because one check passed

B. The pull request is closed without merging

C. The pull request is merged automatically ignoring checks

D. The pull request cannot be merged because one required check failed

Solution

1. Step 1: Understand required status checks behavior

   All required status checks must pass before merging is allowed.

2. Step 2: Analyze the given checks results

   Since ci/lint failed, the pull request cannot be merged despite ci/test passing.

3. Final Answer:

   The pull request cannot be merged because one required check failed -> Option D

4. Quick Check:

   All required checks must pass to merge [OK]

Hint: All required checks must pass to merge PR [OK]

Common Mistakes:

• Assuming one passing check is enough
• Thinking failed checks are ignored
• Believing PR closes automatically on failure

4.

You set required status checks in branch protection, but pull requests are still merging even when checks fail. What is the most likely cause?

medium

A. Required status checks are not selected in the branch protection rule

B. The repository has no branches

C. The checks are passing but showing as failed by mistake

D. The pull request is from the default branch

Solution

1. Step 1: Verify branch protection rule settings

   Required status checks must be explicitly selected in the branch protection rule to enforce them.

2. Step 2: Understand why PRs merge despite failures

   If required checks are not selected, GitHub does not block merges even if checks fail.

3. Final Answer:

   Required status checks are not selected in the branch protection rule -> Option A

4. Quick Check:

   Check if required checks are enabled in protection rules [OK]

Hint: Enable required checks explicitly in branch protection [OK]

Common Mistakes:

• Assuming checks auto-enable without selection
• Thinking repository branch count affects checks
• Confusing default branch with PR source branch

5.

You want to ensure that pull requests cannot be merged unless both ci/build and ci/test pass, but also want to allow admins to override this if needed. How should you configure the branch protection?

hard

A. Enable required status checks for ci/build and ci/test, and allow admin overrides

B. Enable required status checks for ci/build only, no admin override

C. Disable required status checks and require pull request reviews

D. Enable required status checks and disable admin overrides

Solution

1. Step 1: Set required status checks for both ci/build and ci/test

   Both checks must be selected to block merges unless both pass.

2. Step 2: Allow admin overrides in branch protection settings

   This option lets admins merge even if checks fail, providing flexibility.

3. Final Answer:

   Enable required status checks for ci/build and ci/test, and allow admin overrides -> Option A

4. Quick Check:

   Required checks + admin override = Enable required status checks for ci/build and ci/test, and allow admin overrides [OK]

Hint: Select checks and enable admin override in protection rules [OK]

Common Mistakes:

• Selecting only one check instead of both
• Disabling admin override when override is needed
• Confusing pull request reviews with status checks