Skip to content

Commit e9483d8

Browse files
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

File tree

.github/workflows/ci.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,7 @@ jobs:
7171
test:
7272
runs-on: ubuntu-latest
7373
needs: compile
74+
continue-on-error: ${{ matrix.python-version == '3.13' || matrix.python-version == 'pypy-3.11' }}
7475
strategy:
7576
fail-fast: false
7677
matrix:

0 commit comments

Comments
 (0)