Skip to content

ci: run one docs deploy at a time - #202

Merged
rolfjl merged 1 commit into
Python-Ensemble-Toolbox:mainfrom
rolfjl:ci/docs-deploy-concurrency
Nov 19, 2026
Merged

rolfjl merged 1 commit into
Python-Ensemble-Toolbox:mainfrom
rolfjl:ci/docs-deploy-concurrency

Conversation

@rolfjl

@rolfjl rolfjl commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

When several PRs are merged within a minute, each merge starts its own "Publish mkDocs via GitHub Pages" run. Two of them can push to gh-pages at the same time, and one fails:

! [remote rejected] gh-pages -> gh-pages (cannot lock ref 'refs/heads/gh-pages': is at 8e2f27d… but expected 8ff3ea8…)

This happened on 76c63c4 (#201); re-running the job fixed it.

This adds a concurrency group to deploy-docs.yml, so deploys queue instead of overlapping. A running deploy finishes; of those waiting, GitHub keeps only the newest, so the site still ends up at the latest commit.

Not tested: it can only be seen on the next set of merges that land close together.

🤖 Generated with Claude Code

PRs merged in quick succession each start a deploy; two that push to
gh-pages at once race, and one fails with 'cannot lock ref'.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@rolfjl
rolfjl merged commit 1480d09 into Python-Ensemble-Toolbox:main Nov 19, 2026
4 checks passed
@rolfjl
rolfjl deleted the ci/docs-deploy-concurrency branch November 19, 2026 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant