You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: review and auto-merge tier policy for allow-listed PR classes #2574
State which pull request classes may be merged without human review and which never may.
Background
main requires zero approving reviews and two checks (base/issue-branch-policy, Core product validation), consistent with the solo-maintainer position. An agent loop beyond draft PRs needs an explicit allow-list, otherwise autonomy is decided ad hoc.
Next-release planning review of 2026-10-14/15 against main at 7faf6dfb. Tracking: #2555.
This issue is intentionally scheduled for v1.13.0. #2573 remains a prerequisite and #2599 is the security/authority input. The policy must explicitly classify security, credentials, trust, installer, workflow/ruleset, release, and MCP changes as never-auto classes, and must state that an allow-listed path classifier cannot override a sensitive-file or mixed-change finding. This policy is required before any autonomy beyond draft PR preparation; it does not enable auto-merge in this release train.
The governance design review (#2663, PR #2664) recommends closing this as superseded. The design has every PR reviewed and merged by the maintainer, and auto-merge is out of scope. The never-automatic class list in this issue would move into the planned path-to-area map. Ramesh will decide after Codex responds in this thread.
Relayed by Claude Code (Opus 5.5) from Ramesh's answers, posting from Ramesh's account.
Superseded by the accepted governance design in #2664. The design requires a human maintainer to merge every PR, so an allow-list for merging without human review is no longer part of the policy. The sensitive-path and never-automatic boundaries remain in scope for implementation under work packages 9 and 21.
Activity
codeforester commentedon Nov 8, 2026
On hold: don't start implementation yet.
The governance design review (#2663, PR #2664) recommends closing this as superseded. The design has every PR reviewed and merged by the maintainer, and auto-merge is out of scope. The never-automatic class list in this issue would move into the planned path-to-area map. Ramesh will decide after Codex responds in this thread.
Relayed by Claude Code (Opus 5.5) from Ramesh's answers, posting from Ramesh's account.
codeforester commentedon Nov 9, 2026
Superseded by the accepted governance design in #2664. The design requires a human maintainer to merge every PR, so an allow-list for merging without human review is no longer part of the policy. The sensitive-path and never-automatic boundaries remain in scope for implementation under work packages 9 and 21.