Repository navigation
Commit bcacf3b
committed
Scope Flow concurrency per event -- cross-event cancelling showed as a failed check
Cancelling the duplicate across push/pull_request worked, but GitHub reports a cancelled run as a
FAILING check: the PR showed 'Flow-Check pass (1m12s)' alongside 'Flow-Check fail (2s)'. That is
misleading and would block merging under branch protection -- worse than the duplicate it removed.
Grouping per event keeps the useful behaviour (pushing again supersedes your own in-flight run)
without the two triggers cancelling each other. A PR-branch push therefore still runs Flow twice on
the same commit; at ~1m12s that is the cheaper of the two problems.1 parent 49dd5df commit bcacf3b
1 file changed
Lines changed: 9 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
20 | | - | |
21 | | - | |
22 | | - | |
23 | | - | |
24 | | - | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
25 | 28 | | |
26 | 29 | | |
27 | 30 | | |
28 | | - | |
| 31 | + | |
29 | 32 | | |
30 | 33 | | |
31 | 34 | | |
| |||
0 commit comments