Repository navigation
ci: evidence-refresh finishes a running refresh instead of cancelling it on every push (#4703) - #4720
Merged
Merged
Conversation
… it on every push (#4703) A refresh takes about an hour; with cancel-in-progress every merge to main cancelled the running one, so on busy days no refresh completed. GitHub keeps at most one pending run per concurrency group, so the newest push still gets refreshed after the current run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MQNoe4wPJgr7dbUvs3DG6D
Contributor
This was referenced Oct 9, 2026
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
1 participant
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.
Follow-up to #4705 (#4703). The evidence-refresh workflow used
cancel-in-progress: true. A refresh takes ~1 h, so every merge to main cancelled the running one: on 2026-10-08 runs 37849301447, 37850507999, 37850571540 and the manual 37850658519 were all cancelled and no refresh completed. Withcancel-in-progress: falsethe running refresh finishes and GitHub keeps only the newest pending run queued, so the latest main is still refreshed next.One-line change (+ comment). YAML parses.
Part of #4703.
🤖 Generated with Claude Code