rcourtman b0f22f1130 Stop posting retest boilerplate on maintainer issue reopens ... The retest-comment workflow fired on 'reopened' as well as 'opened', and canPostRetestComment gated on the issue author's association, not the reopen actor's. Since non-collaborator reporters cannot reopen maintainer-closed issues, a reopened event is in practice always a deliberate maintainer decision, and the bot would post version-retest boilerplate that contradicts the maintainer's own comment while planting the needs-retest auto-close marker on an issue they chose to keep open (seen on #1471). Restrict the trigger and the guard to 'opened' and pin the reopened skip with a test.		2026-06-11 15:10:33 +01:00
..
issue-version-triage.cjs	Stop posting retest boilerplate on maintainer issue reopens	2026-06-11 15:10:33 +01:00
issue-version-triage.test.cjs	Stop posting retest boilerplate on maintainer issue reopens	2026-06-11 15:10:33 +01:00