Deploy the built website to GitHub Pages instead of the README - #5
Merged
Conversation
Co-authored-by: charles2ke <6725706+charles2ke@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
charles2ke
August 27, 2026 10:05
View session
charles2ke
approved these changes
Aug 27, 2026
There was a problem hiding this comment.
🟡 Changes recommended
The added configure-pages enablement step may fail under the default github.token permissions (blocking deploy) unless an appropriate token/strategy is provided.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR updates the GitHub Pages deployment workflow so the repository publishes the built static site (website/dist) via GitHub Actions, rather than publishing the Jekyll-rendered README.md from the legacy “Deploy from a branch” Pages source.
Changes:
- Adds a
actions/configure-pages@v5step withenablement: trueto enable Pages and switch the Pages source to GitHub Actions before building/deploying. - Keeps the existing build (
npm ci+GITHUB_PAGES=true npm run build) and deploy (upload-pages-artifact+deploy-pages) flow.
File summaries
| File | Description |
|---|---|
| .github/workflows/deploy-pages.yml | Adds a Pages configuration step intended to enable GitHub Pages and switch the source to GitHub Actions before deploying the built site artifact. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+28
to
+34
| - name: Configure GitHub Pages | ||
| uses: actions/configure-pages@v5 | ||
| with: | ||
| # Enables Pages and switches the source to GitHub Actions so the built | ||
| # website is published instead of the Jekyll-rendered README. | ||
| enablement: true | ||
|
|
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
GitHub Pages was still using the legacy "Deploy from a branch" source, so the Jekyll-rendered
README.mdwas published instead of the built website. The Actions deploy job also failed with404 ... Ensure GitHub Pages has been enabled.Changes
actions/configure-pages@v5step (withenablement: true) to.github/workflows/deploy-pages.ymlso Pages is enabled and its source is switched to GitHub Actions, publishingwebsite/distinstead of the README.Validation
npm ci+GITHUB_PAGES=true npm run buildinwebsite/succeeds and producesdist/index.htmlwith correct/GraphQL/base paths.Note: if the workflow token cannot change the Pages setting, set Settings → Pages → Source to "GitHub Actions" once and re-run the workflow.