forked from molecule-ai/molecule-core
dac55f3b42
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>
21 lines
1.0 KiB
Plaintext
21 lines
1.0 KiB
Plaintext
# 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
|