Add CI workflow for backend tests and website lint/build - #18
Merged
Conversation
Co-authored-by: charles2ke <6725706+charles2ke@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
charles2ke
September 5, 2026 04:53
View session
charles2ke
approved these changes
Sep 5, 2026
There was a problem hiding this comment.
🟢 Approval recommended
The workflow configuration matches existing deployment build settings and uses minimal permissions; only a minor README wording clarification is needed.
Pull request overview
Adds a dedicated GitHub Actions CI workflow so backend tests and the website lint/build run on PRs and pushes to main, shifting regressions from “deploy-time/local-only” to “caught in CI”.
Changes:
- Added
.github/workflows/ci.ymlwith two jobs: rootnpm ci && npm test, andwebsite/npm ci && npm run lint && npm run build(withGITHUB_PAGES=true). - Documented the new CI workflow and behavior in
README.md.
File summaries
| File | Description |
|---|---|
.github/workflows/ci.yml |
New CI workflow to run backend tests and website lint/build on PRs and main. |
README.md |
Documents the CI workflow and adds it to the project layout section. |
Review details
- Files reviewed: 2/2 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.
| `GITHUB_PAGES=true npm run build` inside `website/`, matching what the Pages | ||
| deployment builds. | ||
|
|
||
| Runs are grouped per branch and superseded runs are cancelled automatically. |
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
Adds a
CIworkflow so the backend test suite and the website lint/build run automatically. Previously the only committed workflow wasdeploy-pages.yml, which just built and deployedwebsite/— nothing in CI rannpm testornpm run lint, so regressions were only caught locally or at deploy time.Changes
.github/workflows/ci.yml(new)main, all pull requests, andworkflow_dispatch.permissions: contents: readonly.cancel-in-progress: trueso superseded runs are cancelled.package-lock.json,npm ci+npm test.website/package-lock.json,npm ci,npm run lint(Oxlint), andGITHUB_PAGES=true npm run build— mirroring what the Pages deployment builds, so breakage surfaces on the PR instead of at deploy time.README.mdci.ymlto the project layout.Validation
Both jobs' commands were run locally against this branch:
npm ci && npm test→ 42/42 tests passcd website && npm ci && npm run lint→ Oxlint clean, 0 vulnerabilitiescd website && GITHUB_PAGES=true npm run build→ build succeeds (200.37 kB JS / 63.27 kB gzip)CodeQL (
actions) reported 0 alerts.Notes
No Playwright tests exist in this repository (no Playwright config, dependency, or spec files), and this change is CI configuration only with no UI surface, so there are no browser-test screenshots to attach. If you'd like end-to-end coverage of the learning website added to CI, that can be a follow-up.