Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't cancel GHA runs on subsequent push events (Qiskit#9917)
With our switch to using the GitHub merge queue with speculative merging, it's now possible for us to have two push events to a protected branch (like `main`) within a couple of minutes. If this happens, the eager cancellation rules we have set for the coverage and Neko runs in GHA trigger, causing a spurious build failure to appear in the commit logs, and for the coverage history to be lost for one commit. Instead, we can set the cancel-on-update behaviour to only trigger on PR sync events, not branch-push events.
- Loading branch information