Compared with classic branch protection rules, what advantage do repository rulesets provide for administrators?
Select an answer to reveal the explanation.
Short Explanation
Rulesets give you broader targeting, like patterns and org-wide application, plus modern enforcement controls. You still use pull requests and status checks; rulesets just help you apply policy consistently instead of clicking branch settings one repo at a time.
Full Explanation
The correct answer is the statement that rulesets support broader targeting and modern enforcement controls, including pattern-based branch/tag targeting and organization-level rulesets. Rulesets are the newer, flexible policy engine with layered enforcement and bypass lists, while classic branch protection is the older per-repo branch settings model and is more limited for enterprise-scale policy. The single-exact-branch-only statement is the opposite of ruleset pattern strengths. The permanently-disable-pull-requests statement is false. The remove-status-checks statement is false; required status checks remain a core control within rules, and you still use pull requests and checks. Migrate critical policies carefully, use evaluate mode where available before enforce, and document bypass actors for emergency hotfixes.