Add Forgejo Actions CI workflow for tests and build #3

New issue

Closed

opened 2026-07-17 01:17:53 +00:00 by claude-bot · 2 comments

claude-bot commented

2026-07-17 01:17:53 +00:00

Contributor

The repo has no CI. Nothing runs the test suites or the production build on push or PR, which is the main reason Renovate auto-merge is currently unsafe.

Add .forgejo/workflows/ci.yml running on PRs to main and on push to main:

npm ci + npm test (frontend, Node built-in test runner)
npm --prefix backend ci + npm --prefix backend test
npm run build (Vite production build)

Requires an available Forgejo Actions runner. The Dockerfile already runs all three of these during image build, so the workflow is mirroring a known-good sequence.

The repo has no CI. Nothing runs the test suites or the production build on push or PR, which is the main reason Renovate auto-merge is currently unsafe. Add `.forgejo/workflows/ci.yml` running on PRs to `main` and on push to `main`: - `npm ci` + `npm test` (frontend, Node built-in test runner) - `npm --prefix backend ci` + `npm --prefix backend test` - `npm run build` (Vite production build) Requires an available Forgejo Actions runner. The `Dockerfile` already runs all three of these during image build, so the workflow is mirroring a known-good sequence.

claude-bot added this to the v1.1.0 - Test & Ops Hardening milestone

2026-07-17 01:17:53 +00:00

claude-bot added the

ops

testing

labels

2026-07-17 01:17:53 +00:00

claude-bot commented

2026-07-17 01:29:21 +00:00

Author

Contributor

Added .forgejo/workflows/ci.yml. Runs on pull requests to main and pushes to main, with concurrency set so superseded PR runs cancel.

Steps: install + frontend npm test, install + npm --prefix backend test, then npm run build.

Two findings while building it:

Node 20, not 22. Both Dockerfile and backend/Dockerfile pin node:20-alpine. CI matches the deployed runtime rather than a newer version.
No Postgres service needed. All three backend test files (api.test.js, calculation_api.test.js, calculationRunner.test.js) import createMemoryRepository from src/repository.memory.js and pass it to createApp(). None reference repository.pg.js, DATABASE_URL, or any pg client. The suite never touches a live database, so no services: block was added.

Uses npm install rather than npm ci because no lockfiles exist — see #19, which should land before auto-merge is enabled.

Staged in the working tree; not yet committed. Closing when this lands on main and a runner picks up a green run.

Added `.forgejo/workflows/ci.yml`. Runs on pull requests to `main` and pushes to `main`, with `concurrency` set so superseded PR runs cancel. Steps: install + frontend `npm test`, install + `npm --prefix backend test`, then `npm run build`. Two findings while building it: - **Node 20, not 22.** Both `Dockerfile` and `backend/Dockerfile` pin `node:20-alpine`. CI matches the deployed runtime rather than a newer version. - **No Postgres service needed.** All three backend test files (`api.test.js`, `calculation_api.test.js`, `calculationRunner.test.js`) import `createMemoryRepository` from `src/repository.memory.js` and pass it to `createApp()`. None reference `repository.pg.js`, `DATABASE_URL`, or any pg client. The suite never touches a live database, so no `services:` block was added. Uses `npm install` rather than `npm ci` because no lockfiles exist — see #19, which should land before auto-merge is enabled. Staged in the working tree; not yet committed. Closing when this lands on `main` and a runner picks up a green run.

claude-bot referenced this issue

2026-07-17 01:41:03 +00:00

Add CI, Renovate config, changelog, and lockfiles; refresh docs #20

claude-bot commented

2026-07-17 02:00:51 +00:00

Author

Contributor

Done in #20, merged as a0d604b. Corrected in 2804be5 after checking the runner labels actually in use here — ubuntu-latest, not docker, and fully-qualified https://data.forgejo.org/actions/* URLs.

Verified green on a real runner on both #20 and #21.

Done in #20, merged as `a0d604b`. Corrected in `2804be5` after checking the runner labels actually in use here — `ubuntu-latest`, not `docker`, and fully-qualified `https://data.forgejo.org/actions/*` URLs. **Verified green on a real runner** on both #20 and #21.

claude-bot closed this issue

2026-07-17 02:00:52 +00:00

claude-bot referenced this issue

2026-07-17 03:09:27 +00:00

Outage log with detected candidates and coverage assessment #47