Commit e9483d8
committed
Use continue on error for -next jobs
~~Apparently github's automerge is based on the job's properties not
the branch protection rules.~~ From what I gather, seems to make the
overall job succeed even if a specific run fails. This is exactly what
we want.
After checking again the selection was such a pain in the ass I got
one of the status checks wrong in the ruleset, and selected one of the
pypy-3.11 jobs as required. Even after `continue-on-error`-ing and the
overall check now passing the branch still doesn't merge.
`continue-on-error` seems like it's useful regardless, for better
reporting, so leaving it.1 parent 59f36d5 commit e9483d8
1 file changed
Lines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
71 | 71 | | |
72 | 72 | | |
73 | 73 | | |
| 74 | + | |
74 | 75 | | |
75 | 76 | | |
76 | 77 | | |
| |||
0 commit comments