RFC: Fail fast on AppVeyor for repeated commits to the same PR #9355
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.
To cut down on queue times. Opening this to test a few things.
AppVeyor runs:
at the start of a PR build. For queued builds to master we would need some more complicated logic but we might want to build every commit to master separately anyway.
The simple version of this (just checking
$APPVEYOR_REPO_COMMIT
againstgit rev-parse HEAD
) won't work if there's a new commit to master between the time the build gets queued and the time the build starts running, regardless of whether there are any newer commits to the PR branch.