From 4a15c51d044001053756fe309565ae9dc6c164de Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 1 Oct 2026 20:39:46 +0000 Subject: [PATCH] Explain why the auto-merge dispatches deploy.yml dispatch-sync reported no rationale above this lab's gh workflow run line. This adds the fleet's canonical paragraph (a GITHUB_TOKEN merge raises no push event, so the dispatch is what ships the bump). Comment-only. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01P9wNFmWChS4HdDbqrEAq86 --- .github/workflows/deploy.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 956e8c0..e911e87 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -96,6 +96,11 @@ jobs: sleep 15 done [ -n "$merged" ] || { echo "::error::gate passed but the squash merge did not land after 3 attempts; the bump is unmerged and no deploy was dispatched"; exit 1; } + # A merge made with GITHUB_TOKEN raises no push event -- GitHub suppresses + # them so workflows cannot retrigger themselves -- so deploy would never run + # and the site would keep serving the previous build. Ask for it explicitly; + # a workflow_dispatch through the API is not suppressed. The dispatched run + # is the same gate-then-deploy pipeline, so a bad merge still ships nothing. gh workflow run deploy.yml --repo "$GITHUB_REPOSITORY" --ref main env: PR_URL: ${{ github.event.pull_request.html_url }}