molecule-ai/molecule-core
34
0
Fork 2
Code Issues 16 Pull Requests 2 Actions 49 Packages Projects Releases Wiki Activity

chore: add CODEOWNERS to auto-route agent PRs to personal review account

Browse Source 
After landing the 1-required-review gate on staging in cycle 24, every
agent-authored PR sits with `REVIEW_REQUIRED` until someone notices.
CODEOWNERS solves the routing half: every changed path matches `*`, so
GitHub auto-requests review from @hongmingwang-moleculeai (the
personal account, separate from the HongmingWang-Rabbit agent
identity). PRs land in the personal account's notification queue
automatically.

The `*  @hongmingwang-moleculeai` line is informational (route the
request) rather than enforced — branch protection's
require_code_owner_reviews flag is off, so any approving review still
satisfies the 1-review gate. Flip that on later if you want CODEOWNERS
approval to be the *required* review type.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Hongming Wang 2026-04-26 13:40:13 -07:00
parent 9375e3d4ee
commit dac55f3b42
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
.github/CODEOWNERS vendored Normal file
View File

@ -0,0 +1,20 @@
# Default reviewer routing for molecule-core.
#
# `*` matches every changed path, so every PR auto-requests review from
# @hongmingwang-moleculeai. The agent-PR pattern is that the
# HongmingWang-Rabbit (agent) account authors PRs; this file routes
# them into the personal account's review queue automatically — no
# manual `gh pr edit --add-reviewer` per PR.
#
# Why CODEOWNERS instead of branch-protection's review-from-anyone gate:
# the gate just says "1 review needed"; CODEOWNERS specifies *which*
# reviewer the request goes to. Without it, agent PRs sit unreviewed
# until a human happens to look at the queue.
#
# Note: `require_code_owner_reviews` on the staging branch protection
# is currently OFF, so the routing is informational rather than
# enforced. Flip it on (in branch protection settings) if you want
# CODEOWNERS approval to be the *required* review type. Until then,
# any approving review still satisfies the 1-review gate — this just
# makes sure the right person sees it.
* @hongmingwang-moleculeai