Skip to content

ci: run apps/dashboard's own typecheck + tests in CI - #191

Open
kevin-hartman wants to merge 1 commit into
mainfrom
fix/dashboard-ci-job
Open

ci: run apps/dashboard's own typecheck + tests in CI#191
kevin-hartman wants to merge 1 commit into
mainfrom
fix/dashboard-ci-job

Conversation

@kevin-hartman

Copy link
Copy Markdown
Collaborator

What

Adds a dashboard job to .github/workflows/ci.yml so the vendored apps/dashboard app is gated on its own suite.

Why

Root npm test runs vitest over tests/** only — it never installs apps/dashboard deps or runs the app's ~401 vitest tests or its tsc --noEmit, so a dashboard change could regress with a green root CI. This is the coverage gap surfaced during the #190 review.

What the job does

npm ci + npx tsc --noEmit + npx vitest run, working-directory: apps/dashboard, on pull_request/push to main alongside build-and-test. npm ci relies on the now-public apps/dashboard/package-lock.json.

This PR's own CI run exercises the new job.

Root `npm test` covers tests/** only; the vendored apps/dashboard has its own
package.json + vitest (~401 tests) that no CI job ran. Add a `dashboard` job
(npm ci + tsc --noEmit + vitest run, working-directory apps/dashboard) so dashboard
changes are gated on the dashboard's own suite. Runs on pull_request/push to main
alongside build-and-test; npm ci relies on the now-public apps/dashboard lockfile.
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.

1 participant