A pull request can pass API linting and breaking-change checks yet still need design judgment. Code ownership routes changes to specified files, file types, or directories to a designated individual or team for review. When approval is required, a PR touching those paths cannot merge without it. section 8.9 section 8.3
For API definition files and guide documentation, the API governance team can act as code owner. Its review helps catch consistency and standards issues that automated checks may miss. Code owners are notified when a PR needs their attention. section 8.9
To require code-owner review in the illustrated GitHub workflow:
- Add a CODEOWNERS file at the repository root and assign the reviewer to the relevant path, such as chapter8/apis. Commit and merge the file. section 8.5.6
- Give the reviewer repository access, then configure main-branch protection to require PRs, code-owner approval, and successful PR build and minimum-review-criteria status checks. section 8.5.6
- Check that a PR changing the protected path requests code-owner review. A successful build alone does not satisfy the separate approval requirement. section 8.5.6
Keep ownership targeted. Requiring many reviewers outside the team making a change can delay approval; reserve external governance approval for API definitions that need it, and let teams review most other changes internally. Code-owner support depends on the hosting service and may require an add-on. section 8.9
