fix: configure GitHub Pages to use Actions workflow source#113
Merged
eurunuela merged 2 commits intoME-ICA:masterfrom Mar 3, 2026
Merged
Conversation
Add `actions/configure-pages@v4` step to the build job so the workflow self-configures the Pages source on every non-PR run. This prevents silent regression if someone switches Pages settings back to legacy mode in the UI. The immediate fix (switching build_type from legacy to workflow via the GitHub API) has already been applied to the repo settings. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for rica-fmri ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the documentation GitHub Actions workflow to ensure GitHub Pages is configured to use the workflow-based deployment source (vs legacy), preventing regressions where legacy Pages builds take precedence over the deployed MkDocs site.
Changes:
- Adds
actions/configure-pages@v4to the docs workflow build job on non-PR runs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Per review feedback, configure-pages only needs to run when deploying. Moving it to the deploy job (which already has the Pages write/OIDC permissions and the non-PR guard) follows least-privilege and avoids configuring Pages on runs where deployment is skipped. Co-Authored-By: Claude Sonnet 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
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
actions/configure-pages@v4to thebuildjob so the workflow self-configures the Pages source on every non-PR runRoot cause
GitHub Pages was set to legacy mode (
build_type: legacy), serving raw Markdown via Jekyll fromdocs/. Theactions/deploy-pages@v4step was deploying the correct MkDocs/Material site, but the legacy build took precedence — causing 404s on all sub-pages.The immediate fix (switching
build_typefromlegacytoworkflowvia the GitHub API) has already been applied to the repo settings.Test plan
configure-pagesstep🤖 Generated with Claude Code