Add pull-request CI covering clean installation, production build, source and test typechecking, linting, formatting, and the full test suite.
Reference implementation
Model this after webnet/webnet instead of designing a second pipeline from scratch:
.gitea/workflows/ci.yml
.gitea/actions/setup/action.yml
Reuse the same overall shape where it fits: a shared setup action, an install/build job that publishes reusable dependency and build artifacts, then parallel verification jobs that restore those artifacts. Keep lint and formatting checks independent when that avoids unnecessary build dependencies.
Coordinate with the npm-workspaces/Turbo issue so this workflow can use Turbo's cache once the monorepo migration lands, without making initial CI coverage wait unnecessarily.
Acceptance criteria
CI runs on every pull request.
A clean npm ci is required and catches package-lock drift.
The production build runs successfully.
Both application and test TypeScript configurations are checked.
Lint and format-check scripts exist and run in CI.
The complete automated test suite runs in CI.
Repeated jobs do not each redo expensive install/build work when artifacts or Turbo cache can be reused safely.
The configured Node version matches the repository's declared engine.
Job names and failures make the failing gate obvious in the PR UI.
## Goal
Add pull-request CI covering clean installation, production build, source and test typechecking, linting, formatting, and the full test suite.
## Reference implementation
Model this after `webnet/webnet` instead of designing a second pipeline from scratch:
- `.gitea/workflows/ci.yml`
- `.gitea/actions/setup/action.yml`
Reuse the same overall shape where it fits: a shared setup action, an install/build job that publishes reusable dependency and build artifacts, then parallel verification jobs that restore those artifacts. Keep lint and formatting checks independent when that avoids unnecessary build dependencies.
Coordinate with the npm-workspaces/Turbo issue so this workflow can use Turbo's cache once the monorepo migration lands, without making initial CI coverage wait unnecessarily.
## Acceptance criteria
- CI runs on every pull request.
- A clean `npm ci` is required and catches package-lock drift.
- The production build runs successfully.
- Both application and test TypeScript configurations are checked.
- Lint and format-check scripts exist and run in CI.
- The complete automated test suite runs in CI.
- Repeated jobs do not each redo expensive install/build work when artifacts or Turbo cache can be reused safely.
- The configured Node version matches the repository's declared engine.
- Job names and failures make the failing gate obvious in the PR UI.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Add pull-request CI covering clean installation, production build, source and test typechecking, linting, formatting, and the full test suite.
Reference implementation
Model this after
webnet/webnetinstead of designing a second pipeline from scratch:.gitea/workflows/ci.yml.gitea/actions/setup/action.ymlReuse the same overall shape where it fits: a shared setup action, an install/build job that publishes reusable dependency and build artifacts, then parallel verification jobs that restore those artifacts. Keep lint and formatting checks independent when that avoids unnecessary build dependencies.
Coordinate with the npm-workspaces/Turbo issue so this workflow can use Turbo's cache once the monorepo migration lands, without making initial CI coverage wait unnecessarily.
Acceptance criteria
npm ciis required and catches package-lock drift.