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.