Repository navigation
Conversation
Sets cancel-in-progress to false in .github/workflows/agent-leftovers.yml so rapid synchronize and edited webhook events (such as release-please PR updates) run sequentially instead of leaving a stale cancelled check on the PR.
Coverage (unit tests)No unit baseline recorded in
Line and branch coverage from unit test reports. History is recorded in |
This branch has not been deployed
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
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.
Summary
Sets
cancel-in-progress: falsein.github/workflows/agent-leftovers.ymlso back-to-backpull_requestevents queue sequentially instead of cancelling each other.Why
agent-leftovers.ymltriggers ontypes: [opened, synchronize, reopened, edited]and runs in ~4 seconds.release-pleaseupdates a release PR (e.g., #19), it emitssynchronize(push) andedited(title/body update) within a second on the same head SHA.cancel-in-progress: true, the second event cancels the first run and leaves a stalecancelledcheck attached to the PR even though the sibling run passes.cancel-in-progress: falsepreserves sequential ordering (so an older run cannot finish after a newer title/body fix) while letting both runs succeed cleanly.Verification
.github/workflows/;agent-leftovers.ymlis the only workflow combiningeditedtriggers withcancel-in-progress: true.yaml.safe_load.