Question

You are the GitHub Enterprise administrator for an organization that has grown to 200 developers across 15 teams. Leadership wants to standardize the developer workflow so that all production code changes are peer-reviewed by domain owners before merging, while allowing individual teams flexibility on their feature-branch naming. Which approach best establishes an enforceable, consistent review standard across all repositories?

Accepted Answer

Configure organization-level rulesets targeting the default branch that require pull requests with a minimum number of approvals and require review from code owners defined in CODEOWNERS files

Answer

Ask each team lead to manually verify reviews were completed before merging, documented in a shared wiki page

Answer

Disable direct push access for all users at the enterprise account level so no one can push to any branch

Answer

Require each team to create a personal access token policy that blocks merges without approval