Skip to content

Commit 024d495

Browse files
docs(triage): leave protected PRs open (#14852)
1 parent e0db2a5 commit 024d495

2 files changed

Lines changed: 10 additions & 0 deletions

File tree

‎.agents/skills/contribution-triage/SKILL.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,11 @@ trusted policy and reassess changed submission evidence; neither example grants
109109

110110
## Apply the outcome
111111

112+
Do not automatically close a PR if a maintainer in the trusted `TRIAGE_EXEMPTIONS.td` list has
113+
commented or submitted a review, including on earlier heads, or if `triage:keep-open` is present.
114+
Leave protected PRs open for maintainer decision. This does not grant an author exemption,
115+
eligibility, or review approval.
116+
112117
In enforcement mode, execute the applicable outcome within the established scope, using the state and
113118
retry safeguards below. In a dry run or without the required authority, prepare the same action and
114119
comment text but do not write to GitHub. Keep the eligibility finding separate from action completion.

‎CONTRIBUTING.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,11 @@ existing review settings. Neither triage nor a Macroscope review authorizes merg
129129

130130
## Closure and reconsideration
131131

132+
Automated triage leaves a PR open for maintainer decision if someone in the trusted
133+
[TRIAGE_EXEMPTIONS.td](.github/TRIAGE_EXEMPTIONS.td) list has commented or submitted a review,
134+
including on an earlier head, or if `triage:keep-open` is present. This protection does not imply
135+
eligibility or review approval.
136+
132137
PRs that violate these requirements can be closed before deeper review. Multiple independent fixes
133138
require splitting. Missing approval requires maintainer discussion or issue triage, as applicable.
134139
Missing evidence requires establishing the problem and showing how the change was checked.

0 commit comments

Comments
 (0)