[mikepitre]

What & why

• On a PR that changes a protected path, Code owner approval fails until another Team Mobile member approves. CodeRabbit reads that failing check and files it as a Major finding ("Obtain the required Team Mobile approval"), which turns its review into a change request. It approved docs(agents): follow the PR template in pull request descriptions #796 only after the thread was resolved by hand, and it will do the same on every protected-path PR.
• This adds the check and the protected-path comment to REVIEW.md's "Don't flag" list, so CodeRabbit reviews the change itself and approves it if it's fine. The merge still waits for the Team Mobile approval, because Code owner approval is a required check.

Testing

• Docs only. The next protected-path PR shows whether CodeRabbit still flags the check.

Risk

• Low: docs only. CodeRabbit stops commenting on one check. The check itself and the branch rules are unchanged, so a protected-path PR still can't merge without a Team Mobile approval.
• REVIEW.md is in .github/protected-paths, so this PR needs a Team Mobile approval too.

How to revert

• A plain revert is enough.

🤖 Generated with Claude Code

[github-actions]

This pull request changes files listed in .github/protected-paths, so it needs an approval from another Team Mobile member before it can merge. CodeRabbit's approval isn't enough for these files.

• REVIEW.md

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The review instructions now say not to flag a failing Code owner approval check or comments that require Team Mobile approval. They state that approval from CodeRabbit on the latest commit or another Team Mobile member resolves the check.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• clerk/clerk-ios#778: Adds the protected-path comment that the new guidance covers.
• clerk/clerk-ios#773: Adds the Code owner approval check described by the new guidance.
• clerk/clerk-ios#766: Creates REVIEW.md and its review guidance.

Suggested reviewers: seanperez29

Merge Risk: Low · up to 003b6

The guidance can hide actionable approval failures on unprotected paths and should be narrowed to human-approval cases.

Pre-merge checks: 7

Check name	Status	Explanation
Title check		The title "docs(review): don't flag the Code owner approval check" matches the change. The raw summary and objectives show REVIEW.md now lists the Code owner approval check and its protected-path comm…
Description check		The description follows the template's main sections. The "What & why" section explains the problem: a failing Code owner approval check gets filed as a Major finding and turns the review into a chang…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Testing, Risk, And Revert		The PR description includes all three required sections with specific content. Testing says the change is docs-only and identifies the next protected-path PR as validation. Risk explains the docs-only…
Device Evidence		The pull request changes only REVIEW.md. It does not change any file under Sources/ClerkKit/, Sources/ClerkKitUI/, or Examples/E2EHost/. Device evidence is therefore not required.

Full details: Title check

Explanation

The title "docs(review): don't flag the Code owner approval check" matches the change. The raw summary and objectives show REVIEW.md now lists the Code owner approval check and its protected-path comment under the "Don't flag" guidance. The title is specific, short, and names the main change. It uses a conventional commit prefix, which is acceptable.

Full details: Description check

Explanation

The description follows the template's main sections. The "What & why" section explains the problem: a failing Code owner approval check gets filed as a Major finding and turns the review into a change request. It also states the fix and that the merge still waits for Team Mobile approval. The "Testing" section says the change is docs only and names how the next protected-path PR will verify it. The "Risk" section covers the impact and notes that REVIEW.md is in .github/protected-paths. The "How to revert" section says a plain revert is enough. The "What to focus on" section is missing. The template marks it as deletable when the change is trivial, so its absence is acceptable here. The Testing section does not name any test run, but the change is docs only, so this is acceptable too.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Testing, Risk, And Revert

Explanation

The PR description includes all three required sections with specific content. Testing says the change is docs-only and identifies the next protected-path PR as validation. Risk explains the docs-only impact and that branch rules remain unchanged. How to revert says a plain revert is enough. The reviewed diff confirms this is a one-line documentation change in REVIEW.md.

Warning

Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

Recent review info

Automatic approval policy

Commit: 003b66269dae.

Setting	Effective value	Source
Automatic approvals	Enabled	Global configuration
Merge risk	Moderate	Global configuration
Security risk	Not set	Global configuration

Not set means no limit was configured after inheritance. Use @coderabbitai configuration to inspect the resolved settings and their sources.

Run configuration

• Source mode: Auto
• Repository: clerk/clerk-ios
• Branch: review-skip-code-owner-check
• File: .coderabbit.yaml
• Commit: 003b662
• Layers: Repository YAML (base), Organization UI (inherited)
• Review profile: ASSERTIVE
• Plan: Team
• Run ID: 85ac037f-c8b7-4cfc-b6ef-90a2f4415a86

Commits

Reviewing files that changed from the base of the PR and between 197608c and 003b662.

Files selected for processing: 1

• REVIEW.md

Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• clerk/clerk_go (manual)
• clerk/dashboard (manual)
• clerk/accounts (manual)
• clerk/backoffice (manual)
• clerk/clerk (manual)
• clerk/clerk-docs (manual)
• clerk/cloudflare-workers (manual)
• clerk/javascript (auto-detected)

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 6 reviews per hour.