Required status checks in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of enabling required status checks in GitHub?

You enable required status checks on a branch in GitHub. What happens when a pull request is opened without passing these checks?

A The pull request is merged automatically regardless of status checks.

B The pull request cannot be merged until all required status checks pass.

C The pull request is closed automatically by GitHub.

D The pull request is merged but marked as failed.

💡 Hint

Think about what 'required' means for status checks in a branch protection rule.

Required status checks prevent merging pull requests until all checks pass. This ensures code quality and stability.

🧠 Conceptual

intermediate

Which of these is NOT a benefit of required status checks?

Select the option that is NOT a benefit of using required status checks in a Git workflow.

A Ensures code passes tests before merging.

B Prevents broken code from entering main branches.

C Automatically resolves merge conflicts.

D Enforces team quality standards.

💡 Hint

Think about what status checks do versus what merge conflict resolution means.

Required status checks verify code quality but do not handle merge conflicts automatically.

❓ Configuration

advanced

How to configure required status checks on a GitHub branch using CLI?

Which command correctly configures a branch protection rule to require the status check named 'ci/build' on branch 'main' using GitHub CLI?

A gh api repos/:owner/:repo/branches/main/protection -X PUT -f required_status_checks.contexts='["ci/build"]' -f required_status_checks.strict=true

B gh branch protect main --require-status-checks ci/build

C git config branch.main.protection.required_status_checks ci/build

D gh repo set-branch-protection main --status-check ci/build

💡 Hint

GitHub CLI uses 'gh api' to call REST endpoints for advanced settings.

Option A uses the GitHub API via CLI to set required status checks correctly. Other options are invalid commands.

❓ Troubleshoot

advanced

Why does a pull request merge button stay disabled despite passing all checks?

You have required status checks enabled on branch 'develop'. All checks show green, but the merge button is still disabled. What is the most likely cause?

A The branch protection rule requires the branch to be up to date with 'develop' before merging.

B The user does not have write permissions to the repository.

C The status checks are not configured as required in branch protection.

D The pull request is from a fork and cannot be merged.

💡 Hint

Check if the branch protection requires the branch to be updated before merging.

Branch protection can require the branch to be up to date with the base branch before merging, disabling the button until updated.

✅ Best Practice

expert

What is the best practice for required status checks in a team with multiple CI pipelines?

Your team uses multiple CI pipelines for different tests (unit, integration, lint). How should you configure required status checks for the main branch?

A Require only one randomly selected CI pipeline to pass.

B Require only the fastest CI pipeline to pass to speed up merges.

C Require no status checks and rely on manual code review only.

D Require all individual CI pipeline checks to pass before merging.

💡 Hint

Think about ensuring code quality and stability with multiple tests.

Requiring all relevant CI pipelines ensures comprehensive testing and reduces risk of broken code.

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