From 35a09e7612d882307a91d427816955e9f2d9201c Mon Sep 17 00:00:00 2001 From: Tom Boucher Date: Thu, 14 May 2026 10:48:08 -0400 Subject: [PATCH] chore(ci): add 5-day auto-close for awaiting-retest / needs-reproduction (#3506) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds a second job to .github/workflows/stale.yml scoped via only-issue-labels to awaiting-retest and needs-reproduction. days-before-issue-stale=5, days-before-issue-close=0 — when the inactivity threshold trips the stale + close messages fire in the same run. PR side of the action is disabled (-1 sentinel) so this job touches issues only. The existing broad 28+14 job adds awaiting-retest and needs-reproduction to its exempt-issue-labels list so the two jobs do not fight over the same issues. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/stale.yml | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 1009ac17e..924ab7175 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -30,5 +30,29 @@ jobs: with updated reproduction steps on the latest GSD version. stale-issue-label: 'stale' stale-pr-label: 'stale' - exempt-issue-labels: 'fix-pending,priority: critical,pinned,confirmed-bug,confirmed' + exempt-issue-labels: 'fix-pending,priority: critical,pinned,confirmed-bug,confirmed,awaiting-retest,needs-reproduction' exempt-pr-labels: 'fix-pending,priority: critical,pinned,DO NOT MERGE' + + stale-retest: + runs-on: ubuntu-latest + timeout-minutes: 5 + steps: + - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10.2.0 + with: + only-issue-labels: 'awaiting-retest,needs-reproduction' + days-before-issue-stale: 5 + days-before-issue-close: 0 + days-before-pr-stale: -1 + days-before-pr-close: -1 + remove-stale-when-updated: true + stale-issue-message: > + Closing — we asked for a retest / reproduction more than 5 days ago and + haven't heard back. If this is still happening on the latest GSD version + you are welcome to open a new issue with the requested information. + We expect follow-up to maintainer requests within a reasonable window or + we close to keep the tracker actionable. + close-issue-message: > + Closed (not planned) — reporter did not respond within 5 days of our + retest / reproduction request. Re-open with the requested information, + or file a new issue if it still affects you on the latest GSD version. + exempt-issue-labels: 'pinned,priority: critical,fix-pending'