mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-20 02:42:11 +00:00
rcourtman
b0f22f1130
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.
30 lines
834 B
YAML
30 lines
834 B
YAML
name: Issue Version Retest Comment
|
|
|
|
on:
|
|
issues:
|
|
types:
|
|
- opened
|
|
|
|
permissions:
|
|
contents: read
|
|
issues: write
|
|
|
|
jobs:
|
|
comment:
|
|
if: ${{ github.event.issue.pull_request == null }}
|
|
runs-on: ubuntu-24.04
|
|
steps:
|
|
- name: Check out triage helper
|
|
uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
|
|
with:
|
|
sparse-checkout: |
|
|
.github/scripts/issue-version-triage.cjs
|
|
sparse-checkout-cone-mode: false
|
|
|
|
- name: Post retest guidance when needed
|
|
uses: actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b # v7
|
|
with:
|
|
script: |
|
|
const triage = require(`${process.env.GITHUB_WORKSPACE}/.github/scripts/issue-version-triage.cjs`);
|
|
await triage.postRetestComment({ github, context, core });
|