Skip to content

ci(stryker): close the survivors issue when nothing survives - #712

Merged
Chris-Wolfgang merged 2 commits into
mainfrom
ci/stryker-close-survivors-issue-at-zero
Oct 12, 2026
Merged

Chris-Wolfgang merged 2 commits into
mainfrom
ci/stryker-close-survivors-issue-at-zero

Conversation

@Chris-Wolfgang

@Chris-Wolfgang Chris-Wolfgang commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

Summary

#655 is titled "Mutation survivors (0)". The Track surviving mutants step in stryker.yaml only ever edits or creates the kind:mutation-survives issue. So when a run finds no survivors, it retitles the issue to "(0)" and leaves it open indefinitely.

This PR adds one branch: when count is 0, the step closes the open tracking issue with a comment naming the run and the score, then exits. Nothing else changes. Any later run that finds a survivor opens a new issue, as before.

stryker.yaml is a protected file, so this PR changes only that file. repo-template's stryker.yaml has the same gap and needs the same change, in a separate PR there.

Closes #655

Verified (locally)

  • actionlint passes, zizmor --offline reports no findings, and bash -n passes on the extracted step.
  • I ran the extracted step verbatim with a stub gh and a generated mutation-report.json:
Case gh calls made
0 survivors, issue #655 open issue list, then issue close 655 --comment "No surviving mutants in run 9 …"
0 survivors, no open issue issue list only
1 survivor, #655 open issue edit 655 --title "Mutation survivors (1) …" (unchanged behaviour)
1 survivor, no open issue issue create … --label kind:mutation-survives (unchanged behaviour)

Not verified: a real run. The step only runs on non-PR events (schedule or dispatch on main), so the first scheduled run after merge is the end-to-end check.

🤖 Generated with Claude Code

Chris-Wolfgang and others added 2 commits October 12, 2026 13:35
The Track surviving mutants step only ever edited or created the
kind:mutation-survives issue, so a run with zero survivors retitled it
'Mutation survivors (0)' and left it open indefinitely (#655). Now a
zero-survivor run closes the open issue with a comment naming the run
and score; the next run that finds a survivor opens a new one.

Closes #655

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mutation survivors (0) - kill these to raise the score

1 participant