From 8cbd1d537e1ed97ddfd6b9c7ea75968aee2eb751 Mon Sep 17 00:00:00 2001 From: Maximilian Roos Date: Sat, 8 Aug 2026 14:25:12 -0700 Subject: [PATCH] ci: publish the web docs once per release MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A release triggered `publish-web` twice: on the `release` event, and on the push to `web` the release itself makes. The comment behind the `release:` trigger says a push cannot start a workflow, which is true of the default GITHUB_TOKEN but not of `push-web-branch`, which pushes with TEND_BOT_TOKEN. The `web` push run lands second and already decides what is published, so the release-triggered run only repeats work — and, now that `github-pages` requires approval, costs an extra approval. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/publish-web.yaml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/.github/workflows/publish-web.yaml b/.github/workflows/publish-web.yaml index 3cbff0ca0ab4..7d173b5b9171 100644 --- a/.github/workflows/publish-web.yaml +++ b/.github/workflows/publish-web.yaml @@ -1,13 +1,10 @@ name: publish-web on: + # A release ends by pushing its docs to `web` with the bot's PAT, and a push + # made with a PAT does start workflows, so this covers releases too. push: branches: - web - # Even though releases push to `web` branch, that doesn't cause this workflow - # to run, because GHA can't start workflows itself. So we also run on - # releases. - release: - types: [released] # Called by pull-request when specifically requested workflow_call: workflow_dispatch: