Skip to content

Update READMEs and document GitHub Pages publishing - #6

Merged
charles2ke merged 1 commit into
mainfrom
copilot/update-readme-publish-website
Aug 27, 2026
Merged

Update READMEs and document GitHub Pages publishing#6
charles2ke merged 1 commit into
mainfrom
copilot/update-readme-publish-website

Conversation

Copilot AI commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

The READMEs did not reflect the current state of the project: the root README under-documented the website and its Pages deployment, and website/README.md was still the stock Vite template. The learning website itself is already published by .github/workflows/deploy-pages.yml, whose latest run on main deployed successfully to https://charles2ke.github.io/GraphQL/ — no workflow changes were required.

README.md

  • Live Pages URL surfaced at the top.
  • Project structure extended with website/ (App, backendSamples.js, Vite config) and .github/workflows/deploy-pages.yml.
  • Pages section now states the deploy triggers (pushes to main touching website/, plus manual dispatch) and that the workflow enables Pages / switches the source to Actions itself, so no manual repo setup is needed.
  • Added npm run preview and npm run lint next to the existing GITHUB_PAGES=true npm run build.

website/README.md

  • Replaced the default Vite template text with project docs: what the site contains, dev workflow against the local API on port 4000, VITE_GRAPHQL_URL override, a scripts table, and how GITHUB_PAGES=true sets the Vite base to /GraphQL/ to match the project Pages URL.

Documentation-only; no source or workflow files touched.

Co-authored-by: charles2ke <6725706+charles2ke@users.noreply.github.com>
@charles2ke
charles2ke marked this pull request as ready for review August 27, 2026 11:53
@charles2ke
charles2ke requested a lite review from Copilot August 27, 2026 11:53
@charles2ke
charles2ke merged commit 65b3471 into main Aug 27, 2026
1 check passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The PR is described as documentation-only, but it also modifies website/package-lock.json, which should be reverted or explicitly justified/declared.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates repository documentation to better describe the learning website and its GitHub Pages deployment, replacing the default Vite template docs under website/.

Changes:

  • Refreshes README.md to surface the live Pages URL and document the website/ structure + Pages workflow behavior.
  • Rewrites website/README.md with project-specific development, scripts, and deployment guidance.
  • Includes non-documentation changes in website/package-lock.json (lockfile metadata edits).
File summaries
File Description
README.md Adds live site URL and expands documentation for the website + Pages publishing workflow.
website/README.md Replaces stock Vite README with development/scripts/deployment documentation for the website.
website/package-lock.json Lockfile changes unrelated to the stated documentation-only scope.
Review details

Files not reviewed (1)

  • website/package-lock.json: Generated file
  • Files reviewed: 2/3 changed files
  • Comments generated: 2
  • 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 thread website/package-lock.json
Comment on lines 156 to 160
"arm64"
],
"dev": true,
"libc": [
"glibc"
],
"license": "MIT",
"optional": true,
Comment thread website/README.md
Comment on lines +45 to +47
The `.github/workflows/deploy-pages.yml` workflow runs this build and publishes
`dist/` to GitHub Pages on every push to `main` that touches `website/`, and on
manual dispatch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants