ci: run tests on PR and main pushes (not only on release tags) #8

New issue

Closed

opened 2026-07-23 00:12:47 +00:00 by claude-lead-andresmgsl · 0 comments

claude-lead-andresmgsl commented

2026-07-23 00:12:47 +00:00

Member

Problem

.forgejo/workflows/release.yml only runs on push of v* tags. There is no workflow that runs npm test on:

pull requests
pushes to main

That means regressions can land on main without any forge-side gate. Local tests are good (46/46 on audit), but they depend on contributors remembering to run them.

Proposed fix

Add something like .forgejo/workflows/ci.yml:

name: ci
on:
  push:
    branches: [main]
  pull_request:
jobs:
  test:
    runs-on: docker   # match runner labels available on the instance
    container:
      image: node:22-bookworm
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test

Adjust runs-on to whatever labels the heavy-duty Actions runners advertise.

Acceptance

Opening a PR that breaks a test fails the CI job.
Pushing to main also runs the suite.

Audit note

Full audit of stoke @ 92a6741. Related: release automation is fine for publishing; this issue is about continuous quality gates.

## Problem `.forgejo/workflows/release.yml` only runs on `push` of `v*` tags. There is **no** workflow that runs `npm test` on: - pull requests - pushes to `main` That means regressions can land on main without any forge-side gate. Local tests are good (46/46 on audit), but they depend on contributors remembering to run them. ## Proposed fix Add something like `.forgejo/workflows/ci.yml`: ```yaml name: ci on: push: branches: [main] pull_request: jobs: test: runs-on: docker # match runner labels available on the instance container: image: node:22-bookworm steps: - uses: actions/checkout@v4 - run: npm ci && npm test ``` Adjust `runs-on` to whatever labels the heavy-duty Actions runners advertise. ## Acceptance - Opening a PR that breaks a test fails the CI job. - Pushing to `main` also runs the suite. ## Audit note Full audit of stoke @ `92a6741`. Related: release automation is fine for publishing; this issue is about continuous quality gates.