ci/gha: review/fixup auto-cancel settings #1292
Closed
Conversation
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
933bbaa to
9d5f728
Compare
|
Well, that doesn't work as excpted. When pushing to master twice, the previous GHA session isn't cancelled. |
agreppin
pushed a commit
to agreppin/libssh2
that referenced
this pull request
Jul 14, 2024
- use the group expression from `reuse.yml` (via curl). - add auto-cancel for `ci` and `cifuzz`. - add auto-cancel to `appveyor_docker`. I'm just guessing here. The hope is that it fixes AppVeyor CI runs when re-pushing a PR. This frequently caused the freshly pushed session to fail waiting for a connection. - sync group expression in `appveyor_status` with `reuse`. Closes libssh2#1292
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.
reuse.yml(via curl).ciandcifuzz.appveyor_docker. I'm just guessing here.The hope is that it fixes AppVeyor CI runs when re-pushing a PR.
This frequently caused the freshly pushed session to fail waiting for
a connection.
appveyor_statuswithreuse.Closes #1292