ci: every changelog and PR-title check finishes, rather than being cancelled by the next PR edit - #714
Merged
Conversation
…ncelled by the next PR edit Both workflows lose their concurrency group. A run takes seconds, so a run per edit costs little, and the checks list shows one result per event instead of a stack of cancelled runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q8Y8AoPsJCyMsURHvgzm7h
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This replaces #712. The answer to "Is this worth the complexity in ci?" was to remove the concurrency groups instead.
Note
The following content was generated by AI.
changelog.ymlandpr-title.ymllose theirconcurrencygroups, which is 8 lines removed. A PR description edit still starts a run, but no edit cancels the run before it, so the checks list shows finished runs and no cancelled ones.Why this rather than #712, gates
cancel-in-progress: true: each ticked checkbox cancelled the run before it. The run that hung there was a GitHub fault that neither PR prevents.actions: write, and a poll. That is more to maintain than the runs cost.Gates:
pixi run lint, including zizmor on both workflows, passes. The workflows run on this PR.The type is
ci, which owes no changelog line.🤖 Generated with Claude Code
https://claude.ai/code/session_01Q8Y8AoPsJCyMsURHvgzm7h
Generated by Claude Code