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.
Activity