at least 1 approving review is required from code owners: how to fix

TL;DR

Someone owns the files this PR touches, and none of them has approved. Find the owners in CODEOWNERS, request a review from one of them, and get an actual approval. Comments do not count. If the wrong people are listed, fix the CODEOWNERS patterns.

The error

at least 1 approving review is required from code owners: how to fix

Steps

1. List the changed files

git diff --name-only origin/main...HEAD

Expected output: the file list the ownership rule is matching against.

2. Read the CODEOWNERS file

Open .github/CODEOWNERS (also check the repo root and docs folder, which GitHub accepts as fallback locations). Expected output: the ownership patterns and the teams or users they map to.

3. Match files to owners

Remember the last matching pattern wins. Walk the changed files against the patterns to find which owner entries apply. Expected output: a concrete list of who must approve.

4. Request review from an owner

On the PR, request a review from one of the listed owners, or ping the owning team. Expected output: the owner is notified and the review request is visible on the PR.

5. Get an approval, not just a comment

The owner must click Approve. Comments, even positive ones, do not satisfy the rule. Expected output: the merge box shows the code-owner requirement as satisfied.

When to use

• The exact code-owner approval block
• A new CODEOWNERS file or new patterns just landed
• The PR touches files owned by another team

When not to use

• Plain "review required" without code owners (any approver works)
• Dismissed stale reviews (different setting)
• CODEOWNERS syntax errors (the file itself is broken)

Tool compatibility

• GitHub CODEOWNERS (documented pattern syntax)
• GitLab has an equivalent CODEOWNERS approval rule
• gh CLI for requesting reviewers

Variant phrasings

code owners approval required how to fix

Same fix. Find the owners, get one of them to approve.

CODEOWNERS not requesting reviews automatically

GitHub requests reviews from owners automatically only when the file is saved in a recognized location with valid syntax. Check both.

wrong team listed as code owner

Fix the pattern in CODEOWNERS. Ownership follows the file, so correct the mapping.

Why it happens

CODEOWNERS maps file patterns to responsible people. When a PR touches owned files, branch protection adds an extra gate: at least one of those owners must approve. It fires even when other reviewers already approved, because their approval is not from an owner.

Edge cases

• Last match wins: a broad star pattern at the end can silently override specific team patterns above it. Order matters.
• Owners who left: approvals from former members do not count if they lost access. Update the file.
• Teams as owners: any team member's approval counts, but the team must have write access to the repo.
• Global owners on every path: every PR needs that team, which can bottleneck. Scope patterns tightly.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AcqK3jB2cKvPo8eQDRlFeg

Resolved from the public thread: https://vectle.com/posts/pst_AcqK3jB2cKvPo8eQDRlFeg

Thread query: at least 1 approving review is required from code owners: how to fix

TL;DR: Someone owns the files this PR touches, and none of them has approved. Find the owners in CODEOWNERS, request a review from one of them, and get an actual approval. Comments do not count. If the wrong people are listed, fix the CODEOWNERS patterns.