Developer docs
Auto Light Dark
Auto Light Dark

How we use GitHub code owners

Last Updated: November 3, 2026

This document covers how code owners are used to enforce required reviews. The intended audience for this is leads and developers on Product (VFS) teams who want to use code owners to enforce required reviews on their applications.

Platform code owners

We use GitHub's code owners feature to trigger required reviews. A code owner is a GitHub team that must approve a change before it can be merged.

By default, va-platform-frontend is the code owner of vets-website. However, va-platform-backend is the only de facto code owner of vets-api.

Non-Platform code owners

Product teams can optionally create a new GitHub team under the VA GHE GitHub organization by clicking on the New team button. Follow the conventions in the CODEOWNERS configuration file to assign your team to an application folder.

  • New teams need write access to the repo. To request this, ask in #vfs-platform-support.

  • vets-website: a team can be assigned as a code owner of application folders. This will remove va-platform-frontend as a required reviewer when changes are made to those folders. 

  • vets-api: see the CODEOWNERS_README for details.

Codeowner rules

See all of the rules in GitHub's documentation. We’ve highlighted a few of them here:

  • The last matching rule that matches all files in a change takes precedence.

  • Application code should be structured to require as few rules as possible.

  • Only one required reviewer per file can be triggered by code owners rules. A pull request may require multiple code owner approvals.

  • Code owners rules are applied to every push after a PR is created. Required reviewers can be removed during this process but GitHub does not remove a review group once it has been added to a PR as a required reviewer.

  • The Platform teams approve changes to the CODEOWNERS configuration.

  • Your group is responsible for managing its GitHub teams. Since there are many ways to structure a GitHub organization, we recommend being familiar with this feature.

  • We recommend having at least three members on a GitHub team used for code owners. By default, only one code owner group can approve a change.

Team about/description

To facilitate easier review, GitHub team maintainers should add a Slack channel to their GitHub Team details. Like this team has.


Help and feedback