Keep no-op comment runs out of the PR coverage cancellation group

[Copilot]

PR Code Coverage triggers on every issue_comment, and GitHub resolves concurrency at run creation — before the job if: runs. So an ordinary review comment created a run that joined pr-coverage-<n>, cancelled the in-flight pull_request run mid-wait (the artifact wait is up to 1h15m), and then concluded skipped itself. Any PR under review effectively lost its coverage run and showed a red check.

Changes

• Concurrency group is now conditional on whether the run will do work. Runs that the coverage-report job will skip get a unique -noop-<run_id> suffix, so they share a group with nothing and cancel nothing.
• Real runs keep the shared per-PR group, so a new push still supersedes a stale wait — the original intent of cancel-in-progress.
• The predicate mirrors the full job if:, not just the /coverage prefix, so fork pull_request events and non-maintainer comments are also treated as no-ops. A comment marks the two as needing to stay in sync.

concurrency:
  group: >-
    pr-coverage-${{ github.event.pull_request.number || github.event.issue.number }}${{
    !((github.event_name == 'pull_request' &&
    github.event.pull_request.head.repo.full_name == github.repository) ||
    (github.event_name == 'issue_comment' &&
    github.event.issue.pull_request != null &&
    startsWith(github.event.comment.body, '/coverage') &&
    contains(fromJSON('["OWNER","MEMBER","COLLABORATOR"]'), github.event.comment.author_association)))
    && format('-noop-{0}', github.run_id) || '' }}
  cancel-in-progress: true

Skipped runs still appear as skipped exactly as before; only their group membership changes. The folded scalar collapses to a single-line expression, so no newlines leak into the group value.

• Fixes PR coverage run is cancelled by any PR comment, including comments the job skips #279

[Copilot]

Pull request overview

Prevents no-op comment-triggered coverage runs from cancelling active PR coverage runs.

Changes:

• Gives skipped runs unique concurrency groups.
• Preserves per-PR cancellation for real coverage runs.
• Mirrors the job execution predicate in concurrency handling.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[David Engel (David-Engel)]

Heads-up: I have opened #478 as a draft alternative to this PR. They are alternatives — only one should land.

This PR''s no-op shunt is correct and #478 keeps its predicate verbatim, including the point that the predicate should mirror the whole job if: rather than just the /coverage prefix. #478 adds one thing on top: github.event_name in the group key.

The case that motivates it — /coverage comments and ordinary comments are both issue_comment events, and a /coverage run is a real run, so it is not shunted into a -noop- group. It therefore still shares pr-coverage-<n> with an in-flight pull_request run and cancels it. Since only the pull_request run''s check is attached to the PR head SHA, that leaves the same red check this PR is fixing — precisely when a maintainer is manually recovering a report, which is the one moment /coverage gets used.

Scenario	This PR	#478
Ordinary comment cancels in-flight pull_request run	fixed	fixed
Forked-PR / non-maintainer no-op cancels a real run	fixed	fixed
/coverage cancels in-flight pull_request run	still occurs	fixed
New push supersedes a stale pull_request run	preserved	preserved
Second /coverage supersedes the first	preserved	preserved

If you would rather keep this PR''s history, adding -${{ github.event_name }} to the group key here achieves the same thing and I will close #478. Saurabh Singh (@saurabh500) your call.

Context: #266 and #465 were duplicate reports of #279 and are now closed as duplicates.