Which GitHub feature allows you to define which individuals or teams must review a pull request before it can be merged?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Branch protection rules with required reviewers are how you put quality gates on your branches. You specify how many approvals — and optionally which teams — must sign off before anyone can merge. It's your PR approval workflow.
Full explanation below image
Full Explanation
Branch protection rules in GitHub allow repository administrators to configure Required Pull Request Reviews, which mandates that one or more approving reviews are received before a PR can be merged into the protected branch. You can specify the minimum number of required approvals and optionally restrict which users or teams can provide dismissable reviews. While CODEOWNERS also involves designated reviewers, it works in conjunction with branch protection — CODEOWNERS defines who owns which files, and branch protection rules can require code owner approval. Required status checks ensure CI passes, not reviewer approvals. Merge queues manage the order of merges but don't define required reviewers.