ci: add application quality gates to Woodpecker #41

Merged
martin merged 1 commit from ci/quality-gates-22 into main 2026-11-18 17:17:59 +00:00
Owner

Summary

Adds the missing application quality gates as a repository-owned Woodpecker workflow, leaving shared global workflows untouched.

.woodpecker/application-checks.yaml runs on pull requests and on pushes to the default branch (excluding Markdown and the generated catalog file):

  1. Install dependencies — node:24-trixie plus Python 3, using the checked-in Yarn release and --immutable.
  2. Typecheck — yarn tsc.
  3. Lint — yarn lint:all.
  4. Check formatting — yarn prettier:check.
  5. Unit tests — yarn test:ci --runInBand, bounded by a 15-minute timeout that emits a dedicated error before failing.
  6. Build backend — yarn build:backend.

Each check is a separate, named step, so the failing gate is obvious. The workflow is named application-checks, which keeps its results distinct from the global pr-review workflow that still runs alongside it.

The workflow needs no FORGEJO_TOKEN and never runs sync:forgejo, so it is independent of live Forgejo data. It uses the declared Node 24 engine and the vendored Yarn 4.18.1; the Bun migration remains #20.

Validation

  • woodpecker-cli lint .woodpecker/application-checks.yaml — valid
  • Each command executed locally with the same vendored Yarn invocation:
    • install --immutable — pass
    • tsc — pass
    • lint:all — pass
    • prettier:check — pass
    • test:ci --runInBand — 1 suite / 1 test pass
    • build:backend — pass
  • Verified the timeout wrapper returns 124 and reaches the explicit timeout message.

Closes #22

## Summary Adds the missing application quality gates as a repository-owned Woodpecker workflow, leaving shared global workflows untouched. `.woodpecker/application-checks.yaml` runs on pull requests and on pushes to the default branch (excluding Markdown and the generated catalog file): 1. **Install dependencies** — `node:24-trixie` plus Python 3, using the checked-in Yarn release and `--immutable`. 2. **Typecheck** — `yarn tsc`. 3. **Lint** — `yarn lint:all`. 4. **Check formatting** — `yarn prettier:check`. 5. **Unit tests** — `yarn test:ci --runInBand`, bounded by a 15-minute `timeout` that emits a dedicated error before failing. 6. **Build backend** — `yarn build:backend`. Each check is a separate, named step, so the failing gate is obvious. The workflow is named `application-checks`, which keeps its results distinct from the global `pr-review` workflow that still runs alongside it. The workflow needs no `FORGEJO_TOKEN` and never runs `sync:forgejo`, so it is independent of live Forgejo data. It uses the declared Node 24 engine and the vendored Yarn 4.18.1; the Bun migration remains #20. ## Validation - `woodpecker-cli lint .woodpecker/application-checks.yaml` — valid - Each command executed locally with the same vendored Yarn invocation: - `install --immutable` — pass - `tsc` — pass - `lint:all` — pass - `prettier:check` — pass - `test:ci --runInBand` — 1 suite / 1 test pass - `build:backend` — pass - Verified the `timeout` wrapper returns 124 and reaches the explicit timeout message. Closes #22
ci: add application quality gates to Woodpecker
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/application-checks Pipeline was successful
f835964ac1
Add a repository-owned `application-checks` workflow that runs on pull
requests and default-branch pushes. It installs with the checked-in Yarn
release on the declared Node 24 image, then runs typecheck, lint,
formatting, unit tests, and the backend build as separate steps.

The workflow needs no Forgejo token and does not sync the catalog, so it
stays independent of live data. Separate steps plus a dedicated timeout
message make failures identifiable, and the workflow name distinguishes
these checks from the global `pr-review` workflow.

Closes #22

Co-authored-by: OpenCode <opencode@anoma.ly>
martin merged commit 0628484619 into main 2026-11-18 17:17:59 +00:00
martin deleted branch ci/quality-gates-22 2026-11-18 17:17:59 +00:00
Sign in to join this conversation.
No description provided.