Repository navigation
docs: require a merge-risk rating before merging a lanes PR and pilot wide fan-outs - #16609
kyle-sexton wants to merge 2 commits into
Conversation
… wide fan-outs merge.md 4.2.1: a lanes App pull request merges, enqueues or arms --auto only at a head its Merge-Risk line rates. With demote=true the session merges only when an owner decision covers each HIGH or CRITICAL reason; any other reason goes to the owner. AGENTS.md "Merging" points at it. multi-agent config.md, fan-out guard: before a fan-out wider than about four workers, run one pilot worker and confirm plan usage remains, since a usage limit mid-fan-out stops every worker at once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MWmASNT5Knyq99gphnV6B2
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
The Merge-Risk section said nothing reads the record back. That holds for the pipeline, and no longer for a session: the pull-request merge reference now has a session read the rating before it merges a lanes App pull request. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MWmASNT5Knyq99gphnV6B2
Lane run report
Failed GitHub API calls
|
|
claude-security-review reviewed Security review: no issues foundcritical-findings: 0 I read every hunk of all 7 changed files. The pull request changes only documentation and instruction text: three changelog fragments,
Other checks:
|
No related issue: two rules the owner decided in session; no issue tracks them.
Summary
/source-control:pull-request merge§4.2.1 now requires a lanes App pull request to carry a merge-risk rating for the pinned head before a session merges, enqueues or arms--auto. Withdemote=true, the session merges only when an owner decision covers each HIGH or CRITICAL reason; any other reason goes to the owner.AGENTS.md"Merging" points at that rule.reference/config.md, "The fan-out guard": before a fan-out wider than about four workers, run one pilot worker and confirm plan usage remains, since a usage limit mid-fan-out stops every worker at once.Fix
plugins/source-control/skills/pull-request/reference/merge.md: one new §4.2.1 condition. It uses the namesdocs/conventions/pr-pipeline/README.md§ The Merge-Risk line defines (Merge-Risk:line,pr-merge-risk-<pr>-<head>artifact,demote) and points there and at/review:merge-riskinstead of restating them.plugins/multi-agent/reference/config.md: one paragraph at the end of the fan-out guard section, the sectionrouteanddefaults.yamlcite as the guard's owner.AGENTS.md: one pointer sentence in "Merging". No other open PR touchesAGENTS.md.source-controlandmulti-agent.Verification
scripts/validate-plugins.sh --only "source-control multi-agent": all manifests and the catalog validated.scripts/check-changelog-fragments.sh --check-required origin/main: both plugins have a fragment.scripts/check-as-of-recheck.sh --check,scripts/check-cost-figures.sh --check,scripts/check-purged-em-dashes.sh: pass.merge.mdorconfig.md.Related
docs/conventions/pr-pipeline/README.md§ The Merge-Risk line still says nothing reads the record back. This rule is a session rule, not a lane gate, so that file is left unchanged.AGENTS.md, so §4.2.1's merge without asking does not cover it.session: AI Hero
🤖 Generated with Claude Code
https://claude.ai/code/session_01MWmASNT5Knyq99gphnV6B2