The matrix setting effectively duplicates the job. These jobs seem to run in parallel. This can create conflicts when they check out the GitHub Pages branch and try to update it at the same time.
That typically happened with last commit to WebCodecs:
https://github.com/w3c/webcodecs/runs/2462176606
git push --force-with-lease origin "gh-pages"
To https://github.com/w3c/webcodecs.git/
! [remote rejected] gh-pages -> gh-pages (cannot lock ref 'refs/heads/gh-pages': is at a369eebbf6d854fd3815c6bf26afc9e577f47d26 but expected e9dfdfa373befa8cff557a6fd66221ff077ef686)
error: failed to push some refs to 'https://github.com/w3c/webcodecs.git/'
I see that there exists a strategy.max-parallel setting that can probably be set to 1 to serialize the jobs. I don't know if there's a way to do that in spec-prod directly instead of requiring that setting to be set in the YML file.
The
matrixsetting effectively duplicates the job. These jobs seem to run in parallel. This can create conflicts when they check out the GitHub Pages branch and try to update it at the same time.That typically happened with last commit to WebCodecs:
https://github.com/w3c/webcodecs/runs/2462176606
I see that there exists a
strategy.max-parallelsetting that can probably be set to1to serialize the jobs. I don't know if there's a way to do that in spec-prod directly instead of requiring that setting to be set in the YML file.