From 7c65d89e60495c1848ba02bc511881d247ec1e2e Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Thu, 27 Aug 2026 13:15:37 -0700 Subject: [PATCH] fix(ci): stop cancelling in-flight docs publish syncs on main pushes (#131155) Every docs-touching push to main cancelled the in-flight docs-sync-publish run (per-ref concurrency group with cancel-in-progress: true), and cancelled runs leave no successor. Under sustained merge velocity the openclaw/docs mirror never advanced: observed live 2026-08-27 as four consecutive 'completed cancelled' runs while the mirror sat 6 commits behind main. Queue instead of cancel: GitHub keeps only the newest pending run per concurrency group, so bursts still collapse to one follow-up run, and the existing skip_stale_source guard keeps back-to-back completions idempotent. This is the source-to-mirror half of the docs publish starvation bug; the mirror-to-R2 half was fixed in openclaw/docs b4b130bd8. --- .github/workflows/docs-sync-publish.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/docs-sync-publish.yml b/.github/workflows/docs-sync-publish.yml index 2424675033e3..c11358f312b1 100644 --- a/.github/workflows/docs-sync-publish.yml +++ b/.github/workflows/docs-sync-publish.yml @@ -20,8 +20,12 @@ permissions: contents: read concurrency: + # cancel-in-progress starved the mirror: every main push cancelled the in-flight + # sync and cancelled runs leave no successor, so under sustained merge velocity + # openclaw/docs never advanced. Queue instead — GitHub keeps only the newest + # pending run per group, and skip_stale_source keeps completed runs idempotent. group: docs-sync-publish-${{ github.event_name == 'workflow_dispatch' && format('manual-{0}', github.run_id) || github.ref }} - cancel-in-progress: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }} + cancel-in-progress: false jobs: sync-publish-repo: