Repository navigation
Conversation
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
The PR must remain draft until Ben’s repository access is explicitly approved and verified.
Review effort: Balanced
Findings: None
What changed in this PR
Adds Ben and Utkarsh as default code owners for future Relay PRs into main.
Changes:
- Adds a catch-all ownership rule for both developers.
- Documents the separately enforced one-approval requirement.
| File | Description |
|---|---|
.github/CODEOWNERS |
Assigns both developers as owners of all files. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Cloud review-policy dependency check — 12 October 2026Current source head |
Add Ben, Utkarsh, and Parsh as default code owners for future PRs into
main. Any one of them may provide the required developer approval. The active branch ruleset separately requires resolved review conversations, compile/test and secret-scan checks. Automatic Copilot review of ready PRs remains enabled; automatic draft and every-push reviews are disabled.Access dependency: Ben's and Parsh's write-access invitations have been sent and are pending acceptance. Keep this PR draft until GitHub recognizes all three owners and checks pass. Existing R3 PRs have Utkarsh requested; Ben and Parsh will be requested when their invitations are accepted.
Document the agreed effort, review timing, and evidence requirements in
.github/REVIEW_POLICY.md,.github/PULL_REQUEST_TEMPLATE.md, and lean rootAGENTS.md; link the existing contribution guide. Routine changes use Lite. Keys, signing, recovery, backup, authentication, pairing, transactions, migrations, security-critical copy/dependencies/permissions, complex or cross-service changes, and unknown risk use Balanced. Select effort before the first request or ready transition; batch material fixes and stabilize checks before requesting another review.Review record:
d86b0ef2cf25700d63a0ddd11cf281fb2b4dce41. Its substantive overview concern about Ben's access remains tracked by the pending invitation dependency. The new documentation head is not claimed as reviewed.Verification: documentation links, formatting, final newlines, scoped diff, and clean local/remote branch comparisons passed. No runtime files, CI gates, billing, or permissions changed. Agent verification remains proportionate before delivery; human live verification remains retrospective.