Skip to content

fix: avoid nested concurrency collision in publish workflow #667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dem-extra1 merged 1 commit into from
Aug 25, 2026
Merged

fix: avoid nested concurrency collision in publish workflow #667

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions .github/workflows/website-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,11 @@ on:
branches: [main]
workflow_dispatch:

# Serialize deploys so two pushes don't race on the gh-pages branch.
# Cancel in-progress runs on the same branch so we only publish the latest commit.
# The called workflow handles serializing the actual gh-pages git push.
concurrency:
group: gh-pages
cancel-in-progress: false
group: website-publish-${{ github.ref }}
cancel-in-progress: true

jobs:
publish:
Expand Down
Loading