Which two practices help ensure pull requests cannot merge until CI has validated them? (Choose two)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Branch protection or rulesets with required checks (and often require up-to-date branches) gate merges on CI. Deleting tokens or disabling workflows undermines protection instead of enforcing it.
Full explanation below image
Full Explanation
Required status checks make merge buttons wait until named checks report success. These are configured via classic branch protection or modern repository rulesets. Requiring the branch to be up to date before merging ensures checks ran against the latest base branch tip, avoiding merges with stale green checks. Deleting GITHUB_TOKEN is not a merge gate. Disabling workflows removes CI rather than enforcing it. Additional related controls include requiring reviews, signed commits, and restricting who can push. Workflow names and check names must match what protection expects — renaming jobs can break required checks until settings are updated to the new names.