Skip to content

Commit 570c19b

Browse files
fix(ci): serialize concurrent gh-pages deploys
Two master pushes nine seconds apart raced JamesIves' force-push (`cannot lock ref` on gh-pages). The later SHA already deployed; this stops the next pair from failing the same way. Git-Session-Id: a7931123-aeaf-5b22-8f8c-14ffd00e1b70
1 parent 7fd414e commit 570c19b

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

‎.github/workflows/pages.yml‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,15 @@ permissions:
1010
contents: write
1111
pages: write
1212

13+
# Serialize deploys to gh-pages. Concurrent master pushes race the
14+
# JamesIves force-push (cannot lock ref) — run 35056225053 failed at
15+
# 2026-09-16T04:38Z while the next SHA's deploy succeeded 9s later.
16+
# Do not cancel an in-progress master deploy; skip intermediate queued
17+
# runs. Feature-branch builds may cancel superseded in-progress jobs.
18+
concurrency:
19+
group: "${{ github.workflow }}-${{ github.ref }}"
20+
cancel-in-progress: ${{ github.ref != 'refs/heads/master' }}
21+
1322
jobs:
1423
build-and-deploy:
1524
name: Build and deploy (ruby-${{ matrix.ruby_version }})

0 commit comments

Comments
 (0)