ci(docs): self-enable Pages in the deploy workflow - #3
Merged
Conversation
The first post-merge `docs-deploy` run failed at "Configure Pages" because GitHub Pages was not yet enabled as a GitHub-Actions source at that moment, so the stale default-Jekyll build of the README kept serving instead of the mkdocs-material site. Set `enablement: true` on actions/configure-pages so the workflow enables Pages itself on first run and can't fail that way again (no-op once Pages is configured). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
The first post-merge
docs-deployrun failed at Configure Pages because Pages wasn't yet enabled as a GitHub-Actions source at merge time — so GitHub's default Jekyll build of the README kept serving instead of the mkdocs-material site (which is why the live page didn't resemble the sibling). I've since re-triggered the deploy and the site is now live and correct.This one-line change sets
enablement: trueonactions/configure-pages@v5so the workflow enables Pages itself on first run and can't fail that way again. No-op once Pages is configured.🤖 Generated with Claude Code