Skip to content

Add GitHub Actions CI workflow for lint and tests (#79) - #447

Draft
stephaniehobson wants to merge 5 commits into
441--update-toolchainfrom
79--github-actions-ci
Draft

stephaniehobson wants to merge 5 commits into
441--update-toolchainfrom
79--github-actions-ci

Conversation

@stephaniehobson

@stephaniehobson stephaniehobson commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

Runs lint (ESLint + stylint), the Vitest unit suite, and the full Playwright end-to-end suite on every push to main and every pull request, via a single "CI" workflow with two jobs.

Based on springfield where possible.

@stephaniehobson
stephaniehobson added this pull request to stack #445 September 18, 2026 23:32
@stephaniehobson stephaniehobson changed the title Add CI based on GitHub Actions Add GitHub Actions CI workflow for lint and tests (#79) Sep 18, 2026
@stephaniehobson
stephaniehobson marked this pull request as draft September 18, 2026 23:39
@stephaniehobson
stephaniehobson force-pushed the 79--github-actions-ci branch 4 times, most recently from 5831bff to f846c70 Compare September 21, 2026 17:40
@stephaniehobson
stephaniehobson requested a lite review from Copilot September 21, 2026 17:40

This comment was marked as outdated.

This comment was marked as outdated.

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.

Copilot review overview

🟡 Changes recommended

Blocking E2E checks depend on live third-party URLs, and the ExecPlan contains stale records and a missing revision note.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1 High severity · 1 Medium severity · 4 Low severity

Open (6)

Comment thread .github/workflows/ci.yml
- name: "Install Playwright browsers"
run: npx playwright install --with-deps chromium
- name: "Run end-to-end tests"
run: npm run test:playwright
Comment on lines +321 to +325
than smoothed over: two of these specs (`contact.spec.js`'s "All links work",
`footer.spec.js`'s "All footer links work") check real, live external URLs and have, in the past
(documented in PR #444's own `docs/execplans/2026-09-15-update-toolchain.md`), failed for reasons
external to this repository — a dead forum link, a redirect target that blocks non-browser HTTP
clients. Both passed cleanly in this session's own run. If either becomes a recurring source of a
@stephaniehobson
stephaniehobson force-pushed the 79--github-actions-ci branch 2 times, most recently from f2ad5c9 to b224c69 Compare September 22, 2026 17:52
The final jump in this string of redirects blocks bots so we'll back up
one step and test that the redirect is configured (that we get a 301)
and not test the entire redirect path. Just for this link.

This branch has not been deployed

No deployments
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.

2 participants