What can push rulesets help prevent at the repository or organization level?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Push rulesets put guardrails on what lands in Git — paths, file sizes, file extensions, and other push-time constraints depending on configuration — before bad content becomes history everyone clones. They are about push compliance, not banning people from reading docs or filing issues.
Full explanation below image
Full Explanation
The correct answer is preventing unauthorized or non-compliant pushes according to configured constraints. Push rulesets extend policy beyond classic 'who can push to main' into content-oriented or push-time controls useful for enterprises (for example restricting sensitive paths or file types when configured). Option B is unrelated. Option C is wrong; issues are a different permission surface. Option D is unrelated to push policy. Combine push rulesets with CODEOWNERS, required reviews, and secret push protection for defense in depth.