ci: Trigger Pages deploy from Release workflow#299
Draft
rubberduck203 wants to merge 4 commits intomainfrom
Draft
ci: Trigger Pages deploy from Release workflow#299rubberduck203 wants to merge 4 commits intomainfrom
rubberduck203 wants to merge 4 commits intomainfrom
Conversation
Pages hasn't deployed since January because the tag glob pattern in gh-page.yml didn't match the new CalVer+build metadata tags. Instead of fixing the pattern, call gh-page.yml directly from the Release workflow via workflow_call — this is more reliable and makes the dependency explicit. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Also add CLAUDE.md to remind AI assistants to keep the README in sync when workflows are modified. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update URL, organizationName, editUrl, and GitHub links to point at the Gusto org after the repo transfer. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Gusto's org has a custom domain for GitHub Pages. 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
gh-page.yml— it hasn't matched since the CalVer format changed in Februarygh-page.ymldirectly from the Release workflow viaworkflow_calldocusaurus.config.tsto point atGustoorg (was still referencingoscope-dev)Blocked: GitHub Pages domain issue
GitHub Pages is enabled for the repo, but the Gusto org has a custom domain (
docs.gusto.com) configured for Pages. That means this repo's docs would be served atdocs.gusto.com/scope/, which is a problem becausedocs.gusto.comis Gusto's official public API documentation portal for customers and partners. An internal dev tool's docs shouldn't live there.Options to resolve
scope-docs.gusto.com) — requires DNS work and org admin helpContext
oscope-devtoGustooscope-devorg had no custom domain, so Pages worked atoscope-dev.github.io/scope/Gusto/gistsrepo (internal visibility) gets an anonymized URL, but public repos are forced throughdocs.gusto.comWhy Pages was broken before the domain issue
The
Build Github Pagesworkflow triggered on tags matching'**[0-9]+.[0-9]+.[0-9]+*'. Old tags likev2026.1.12matched. New tags likev2026.4.8+1002do not — the+breaks the glob.Test plan
workflow_dispatch— Pages build step succeeds🤖 Generated with Claude Code