ci: fix docs publishing by removing tag indirection#207
Merged
gtrivedi88 merged 1 commit intoMay 13, 2026
Conversation
The previous workflow used a two-step process: the tag job force-tagged the commit as `docs`, expecting the tag push to trigger build and deploy jobs. This never worked because GitHub Actions does not trigger workflows from tag pushes made with GITHUB_TOKEN (by design, to prevent loops). Fix: run check, build, and deploy as sequential jobs in a single workflow invocation. The check job determines if the pushed branch is the latest release branch, and build/deploy gate on its output. Also update docs/README.md to reflect the new workflow design. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cherry-pick of the publishing fix from #206 (targeting
release-0.1) tomain, so both branches stay in sync.GITHUB_TOKEN(by design, to prevent recursive loops). Thetagjob successfully created the tag, but the tag push never triggered thebuildanddeployjobs.check→build→deployas sequential jobs in a single workflow invocation, gated on thecheckjob's output.See #206 for full details.
Test plan
validatejob) still runs on PRs tomain🤖 Generated with Claude Code