From 570c19bc08a69bb2ae72a74c605ee325e12e245c Mon Sep 17 00:00:00 2001
From: Bob <bob@superuserlabs.org>
Date: Wed, 16 Sep 2026 05:01:59 +0000
Subject: [PATCH] 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
---
 .github/workflows/pages.yml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml
index 0fcdfee719..f93130cf15 100644
--- a/.github/workflows/pages.yml
+++ b/.github/workflows/pages.yml
@@ -10,6 +10,15 @@ permissions:
   contents: write
   pages: write
 
+# Serialize deploys to gh-pages. Concurrent master pushes race the
+# JamesIves force-push (cannot lock ref) — run 35056225053 failed at
+# 2026-09-16T04:38Z while the next SHA's deploy succeeded 9s later.
+# Do not cancel an in-progress master deploy; skip intermediate queued
+# runs. Feature-branch builds may cancel superseded in-progress jobs.
+concurrency:
+  group: "${{ github.workflow }}-${{ github.ref }}"
+  cancel-in-progress: ${{ github.ref != 'refs/heads/master' }}
+
 jobs:
   build-and-deploy:
     name: Build and deploy (ruby-${{ matrix.ruby_version }})