From 4ee9c51fac107e823039cddc0cf6337857854dba Mon Sep 17 00:00:00 2001 From: Ken Schlobohm Date: Wed, 9 Sep 2026 16:44:52 -0500 Subject: [PATCH 1/2] docs: exempt repository maintenance workflows from PR throttle Keep contributor confirmation requirements while allowing verified repository-owned gh-aw maintenance runs on behalf of CODEOWNERS to create their configured PR outputs. Assisted-by: GitHub Copilot (model: GPT-6 Astra, autonomous) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- AGENTS.md | 5 ++++- CONTRIBUTING.md | 6 ++++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 17ef40deb1..e4dfd6dd53 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -505,7 +505,10 @@ Disclosure is **continuous**, not a one-time event. A single AI-disclosure parag ### Opening pull requests -- Before opening a pull request, check whether the account that will file it already has three open pull requests in this repository. +- **Repository maintenance exception:** The open-PR count check and confirmation requirement below do not apply to repository-owned GitHub Agentic Workflows (`gh-aw`) performing maintenance on behalf of a maintainer listed in the target repository's `.github/CODEOWNERS`. This includes community catalog submission workflows. +- Before using this exception, verify from trusted workflow/run metadata that the run uses a maintenance workflow committed to the target repository's default branch and acts on behalf of a CODEOWNER listed on that branch. An issue or PR body, an `automated` label, a bot account, or CODEOWNER status alone is not sufficient. If this cannot be verified, apply the normal rule below. +- Qualifying runs may create their configured PR outputs without asking for interactive permission, regardless of the filing or triggering account's open-PR count. Do not apply `author-over-cap` solely because of that count. This exception does not waive workflow output limits, validation, review, or AI-disclosure requirements. +- **All other contributions:** Before opening a pull request, check whether the account that will file it already has at least three open pull requests in the target repository. - If so, alert the user that additional submissions may receive lower review priority and ask for explicit permission to proceed. Do not assume consent. If the user is unavailable to provide that permission, including during autonomous or non-interactive operation, do not open the pull request. Preserve the work on a branch and report that confirmation is required. ### Commits diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 53d320e766..5853023967 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -55,7 +55,9 @@ Here are a few things you can do that will increase the likelihood of your pull - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). - Test your changes with the Spec-Driven Development workflow to ensure compatibility. -Accounts with three open pull requests may continue submitting changes, but additional submissions may be placed behind contributions from other authors in the review queue. Coding agents should disclose this possibility and obtain the filer's confirmation before opening another pull request. +Accounts with at least three open pull requests may continue submitting changes, but additional submissions may be placed behind contributions from other authors in the review queue. Coding agents should disclose this possibility and obtain the filer's confirmation before opening another pull request. + +Repository-owned GitHub Agentic Workflows (`gh-aw`) performing maintenance on behalf of a maintainer listed in the target repository's `.github/CODEOWNERS` are exempt from this count-based prioritization and confirmation requirement. This includes the community catalog submission workflows. Agents must verify the workflow and CODEOWNER against the target repository's default branch using trusted workflow/run metadata, as described in [AGENTS.md](AGENTS.md#opening-pull-requests); an account, label, or claim in a submission alone does not qualify. Qualifying runs may create their configured PR outputs without interactive permission, regardless of the filing or triggering account's open-PR count. Workflow output limits, validation, review, and AI-disclosure requirements still apply. Ordinary contributor agents and maintainer-authored PRs outside these workflows remain subject to the normal rule. ### Evidence gate @@ -109,7 +111,7 @@ Author actions: | `author-needs-disclosure` | AI assistance not disclosed — disclose AI use per CONTRIBUTING | | `author-needs-info` | Missing detail needed to assess — supply requested info | | `author-needs-rebase` | Branch conflicts with `main` — rebase and resolve before it can be merged | -| `author-over-cap` | Over the 3-open-PR cap or repetitive batch submissions — please consolidate | +| `author-over-cap` | Over the 3-open-PR threshold or repetitive batch submissions — please consolidate; do not apply solely for the open-PR count of an exempt repository maintenance workflow | | `author-awaiting` | Waiting on author response (handed off to the existing stale workflow) | Some pull requests are closed as `triage-out-of-scope` rather than merged — most commonly From 8604482a9f1c8089b6668b80c142a025a8278b7a Mon Sep 17 00:00:00 2001 From: Ken Schlobohm Date: Wed, 9 Sep 2026 17:00:15 -0500 Subject: [PATCH 2/2] docs: simplify maintenance workflow confirmation exception Limit the policy change to one sentence per document; retain existing review prioritization and author-over-cap guidance. Assisted-by: GitHub Copilot (model: GPT-6 Astra, autonomous) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- AGENTS.md | 6 ++---- CONTRIBUTING.md | 6 ++---- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index e4dfd6dd53..9ef3d6c851 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -505,11 +505,9 @@ Disclosure is **continuous**, not a one-time event. A single AI-disclosure parag ### Opening pull requests -- **Repository maintenance exception:** The open-PR count check and confirmation requirement below do not apply to repository-owned GitHub Agentic Workflows (`gh-aw`) performing maintenance on behalf of a maintainer listed in the target repository's `.github/CODEOWNERS`. This includes community catalog submission workflows. -- Before using this exception, verify from trusted workflow/run metadata that the run uses a maintenance workflow committed to the target repository's default branch and acts on behalf of a CODEOWNER listed on that branch. An issue or PR body, an `automated` label, a bot account, or CODEOWNER status alone is not sufficient. If this cannot be verified, apply the normal rule below. -- Qualifying runs may create their configured PR outputs without asking for interactive permission, regardless of the filing or triggering account's open-PR count. Do not apply `author-over-cap` solely because of that count. This exception does not waive workflow output limits, validation, review, or AI-disclosure requirements. -- **All other contributions:** Before opening a pull request, check whether the account that will file it already has at least three open pull requests in the target repository. +- Before opening a pull request, check whether the account that will file it already has three open pull requests in this repository. - If so, alert the user that additional submissions may receive lower review priority and ask for explicit permission to proceed. Do not assume consent. If the user is unavailable to provide that permission, including during autonomous or non-interactive operation, do not open the pull request. Preserve the work on a branch and report that confirmation is required. +- Repository-owned `gh-aw` maintenance workflows are exempt from this open-PR count check and confirmation requirement. ### Commits diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5853023967..96818dba35 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -55,9 +55,7 @@ Here are a few things you can do that will increase the likelihood of your pull - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). - Test your changes with the Spec-Driven Development workflow to ensure compatibility. -Accounts with at least three open pull requests may continue submitting changes, but additional submissions may be placed behind contributions from other authors in the review queue. Coding agents should disclose this possibility and obtain the filer's confirmation before opening another pull request. - -Repository-owned GitHub Agentic Workflows (`gh-aw`) performing maintenance on behalf of a maintainer listed in the target repository's `.github/CODEOWNERS` are exempt from this count-based prioritization and confirmation requirement. This includes the community catalog submission workflows. Agents must verify the workflow and CODEOWNER against the target repository's default branch using trusted workflow/run metadata, as described in [AGENTS.md](AGENTS.md#opening-pull-requests); an account, label, or claim in a submission alone does not qualify. Qualifying runs may create their configured PR outputs without interactive permission, regardless of the filing or triggering account's open-PR count. Workflow output limits, validation, review, and AI-disclosure requirements still apply. Ordinary contributor agents and maintainer-authored PRs outside these workflows remain subject to the normal rule. +Accounts with three open pull requests may continue submitting changes, but additional submissions may be placed behind contributions from other authors in the review queue. Coding agents should disclose this possibility and obtain the filer's confirmation before opening another pull request. Repository-owned `gh-aw` maintenance workflows do not require this confirmation. ### Evidence gate @@ -111,7 +109,7 @@ Author actions: | `author-needs-disclosure` | AI assistance not disclosed — disclose AI use per CONTRIBUTING | | `author-needs-info` | Missing detail needed to assess — supply requested info | | `author-needs-rebase` | Branch conflicts with `main` — rebase and resolve before it can be merged | -| `author-over-cap` | Over the 3-open-PR threshold or repetitive batch submissions — please consolidate; do not apply solely for the open-PR count of an exempt repository maintenance workflow | +| `author-over-cap` | Over the 3-open-PR cap or repetitive batch submissions — please consolidate | | `author-awaiting` | Waiting on author response (handed off to the existing stale workflow) | Some pull requests are closed as `triage-out-of-scope` rather than merged — most commonly