Checking access…

Skip to main content
Version: v2

Documentation Owners

This guide explains who owns each documentation area and how to update ownership rules safely.

File Location​

The repository CODEOWNERS file is at:

  • .github/CODEOWNERS

GitHub uses this file to automatically request reviews when a pull request changes matching files.

How Matching Works​

CODEOWNERS follows simple but strict matching behavior:

  • The last matching rule wins
  • Put general rules first and specific overrides after
  • Use / at the start to anchor to repository root
  • Use trailing / for directories

Examples:

  • /docs/03-developers/ matches all developer docs
  • /docs/03-developers/2-Migration/ overrides ownership for that sub-area when listed later

Ownership Reference​

Use this table as the quick ownership map for documentation and related platform paths.

PathAreaTeam
* (default)Entire repository fallbackAll teams
/.github/workflows/CI/CD workflowsPlatform / Infra team
/CODEOWNERSOwnership configPlatform / Infra team
/src/ /config/ /scripts/ /plugins/ /docusaurus.config.jsApp source & build configPlatform / Infra team
/openapi/API specificationsBusiness team · QA team · Back-end team
/docs/03-developers/Developer docs (general)Back-end team
/docs/03-developers/2-Migration/Migration guidesBack-end team
/docs/03-developers/4-convenient-checkout-ui/UI integration docsUI team
/docs/03-developers/4-convenient-checkout-api/API integration docsBack-end team
/docs/03-developers/5-convenient-checkout-api/4-error-codes/API error codesBusiness team · QA team
/docs/03-developers/14-Security/Security docs (encryption, key management)Back-end team
/docs/01-business/Business docsBusiness team
/docs/05-engineering-guide/Engineering guideBack-end team
/docs/06-high-level-designs/High-level designsArchitect
/docs/07-contributing-guide/Contributing guideAll teams
/docs/09-Testing/Testing docsQA / Testing team
/docs/10-announcements/AnnouncementsPlatform / Infra team

Safe Update Process​

When editing CODEOWNERS:

  1. Confirm the target path exists in the repo (folder names must match exactly).
  2. Add or update rules using anchored paths (for example, /docs/07-contributing-guide/).
  3. Preserve parent-before-child ordering so specific rules can override correctly.
  4. Keep comments updated so section intent is clear.
  5. Open a pull request and verify requested reviewers match expectations.

Common Mistakes To Avoid​

  • Wrong folder names (for example, 9-Testing instead of 09-Testing)
  • Placing a broad rule below a specific one, which accidentally overrides it
  • Omitting trailing / on directory rules when directory intent is expected
  • Duplicating owner handles unnecessarily
  • Changing ownership behavior without documenting the reason in comments or PR notes