Skip to content

Cancel superseded PR CI runs - #64

Merged
ChrisRackauckas merged 1 commit into
mainfrom
ci-cancel-superseded
Oct 17, 2026
Merged

ChrisRackauckas merged 1 commit into
mainfrom
ci-cancel-superseded

Conversation

@ChrisRackauckas

@ChrisRackauckas ChrisRackauckas commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

🚧 UNREVIEWED — awaiting review by @ChrisRackauckas. Filed by an AI agent running as @ChrisRackauckas; Chris has not seen this.
Harness: Claude Code 2.1.302 · Model: claude-sonnet-5-5
Conversation: local subagent of the fleet-master session (no published session URL)

This PR should be ignored until reviewed by @ChrisRackauckas.

Adds a top-level concurrency group with cancel-in-progress to the pull_request workflows that lack one, so a new push to a PR cancels that PR's superseded run. cancel-in-progress is true only for pull_request events, so pushes to the default branch, tags and scheduled runs never cancel each other.

Workflows changed:

  • DependabotAutoMerge.yml
  • DocPreviewCleanup.yml
  • RunicSuggestions.yml
  • SpellCheck.yml
  • benchmark.yml

Workflows skipped:

  • none

Verification: every edited file parses as YAML and differs from the original only by the concurrency key (checked programmatically). CI itself is the runtime check; I have not run the workflows locally.

Risk assessment

  • Risk: low (L3: CI configuration)
  • Blast radius: PR CI runs only; no source, test or public API change. Pushes to the default branch, tags and schedules are unaffected by the conditional.
  • Evidence: YAML round-trip check; an equivalent group with a startsWith(github.ref, 'refs/pull/') condition is already used by the existing CI workflows in these repos.
  • Independent review: Codex gpt-6.1-sol rated it low (L3), high confidence: mechanical, PR-only CI configuration change with valid YAML and no group collision with the reusable workflows. It noted that a queued (not running) default-branch run can be replaced by a newer push to the same group, which cancel-in-progress: false does not prevent; that is the same behaviour as the existing startsWith(github.ref, 'refs/pull/') pattern.
  • Merge: auto-merge candidate after an independent review

🤖 Posted by an AI agent — harness: Claude Code 2.1.302 · model: claude-sonnet-5-5
Conversation: local subagent of the fleet-master session (no published session URL)

Add a cancel-in-progress concurrency group, active only for pull_request events, to the PR workflows that lack one.

Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Agent-Harness: Claude Code 2.1.302
Agent-Model: claude-sonnet-5-5
Agent-Session: local subagent of the fleet-master session
@ChrisRackauckas
ChrisRackauckas marked this pull request as ready for review October 17, 2026 16:31
@ChrisRackauckas
ChrisRackauckas merged commit 60ec8aa into main Oct 17, 2026
14 checks passed
@ChrisRackauckas
ChrisRackauckas deleted the ci-cancel-superseded branch October 17, 2026 16:31
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.

1 participant