ci: add test workflow #275

Open

ci-bot wants to merge 12 commits from ci/add-test-workflow into main

pull from: ci/add-test-workflow

merge into: projects:main

projects:main

Conversation 1 Commits 12 Files changed 4 +56 -1

ci-bot commented 2026-09-10 20:22:13 +00:00

Member

• Copy link
• Copy Markdown

Adds the missing Forgejo workflow files to run the test suite in CI, plus a small fix so pnpm test actually exists (the README already references it).

What's in it

• .forgejo/workflows/test.yaml — runs on every PR to main:
  • unit job on srv-generic (same ci-pnpm container as the other checks): pnpm test:unit
  • integration job on srv-home with a services: Forgejo instance (pinned 16.0.3-rootless, same image as the devcontainer): pnpm test:integration
• package.json — adds the test script (pnpm test:unit) that the README's Testing section already documents.

How the integration job works

• The Forgejo service container is started via the services: keyword (act_runner supports it like GitHub Actions); the job container reaches it at http://forgejo:3000 on the shared job network — the same URL the tests hardcode in src/test/integration/shared.ts.
• The service entrypoint mirrors .devcontainer/docker-compose.yaml exactly: docker-setup.sh → forgejo migrate → create the test-bot user (the credentials from src/test/integration/forgejo.env) → forgejo web.
• src/test/integration/setup.ts already waits for /api/healthz and seeds the repo deterministically, so no extra provisioning step is needed.
• No published ports: the job container uses the internal service network, so concurrent PRs on the same runner can't collide on port 3000.

Checks

pnpm check / lint:check / format:check ✅, pnpm test:unit 34/34 ✅. The integration job itself can't run from this environment (no Forgejo instance here) — it needs the runner, which is exactly what this workflow provides.

⚠️ One thing to verify on the runner: the options: entrypoint override for the service (--entrypoint sh -c "..."). It's the same entrypoint the devcontainer uses, but if act_runner mangles the quoted string, the fallback is a root docker-compose.test.yaml + docker compose up step on the runner. Happy to switch if it misbehaves.

Adds the missing Forgejo workflow files to run the test suite in CI, plus a small fix so `pnpm test` actually exists (the README already references it). ## What's in it - **`.forgejo/workflows/test.yaml`** — runs on every PR to `main`: - **unit** job on `srv-generic` (same `ci-pnpm` container as the other checks): `pnpm test:unit` - **integration** job on `srv-home` with a `services:` Forgejo instance (pinned `16.0.3-rootless`, same image as the devcontainer): `pnpm test:integration` - **`package.json`** — adds the `test` script (`pnpm test:unit`) that the README's Testing section already documents. ## How the integration job works - The Forgejo service container is started via the `services:` keyword (act_runner supports it like GitHub Actions); the job container reaches it at `http://forgejo:3000` on the shared job network — the same URL the tests hardcode in `src/test/integration/shared.ts`. - The service entrypoint mirrors `.devcontainer/docker-compose.yaml` exactly: `docker-setup.sh` → `forgejo migrate` → create the `test-bot` user (the credentials from `src/test/integration/forgejo.env`) → `forgejo web`. - `src/test/integration/setup.ts` already waits for `/api/healthz` and seeds the repo deterministically, so no extra provisioning step is needed. - No published ports: the job container uses the internal service network, so concurrent PRs on the same runner can't collide on port 3000. ## Checks `pnpm check` / `lint:check` / `format:check` ✅, `pnpm test:unit` 34/34 ✅. The integration job itself can't run from this environment (no Forgejo instance here) — it needs the runner, which is exactly what this workflow provides. ⚠️ One thing to verify on the runner: the `options:` entrypoint override for the service (`--entrypoint sh -c "..."`). It's the same entrypoint the devcontainer uses, but if act_runner mangles the quoted string, the fallback is a root `docker-compose.test.yaml` + `docker compose up` step on the runner. Happy to switch if it misbehaves.

ci-bot added 1 commit 2026-09-10 20:22:13 +00:00

ci: add test workflow e242860cff

ci-bot referenced this pull request 2026-09-10 20:22:21 +00:00

tests #264

davide added 1 commit 2026-09-10 22:31:20 +00:00

chore: separate files 07ea1b67ab

davide added 1 commit 2026-09-10 22:34:54 +00:00

chore: fix job 7a241fd9ec

davide added 1 commit 2026-09-10 22:38:03 +00:00

chore: fix job d079dfb55a

davide added 1 commit 2026-09-10 22:56:14 +00:00

chore: fix job 2c5d444f76

davide added 1 commit 2026-09-10 22:57:26 +00:00

chore: fix job 6d04d02815

davide added 1 commit 2026-09-10 23:00:01 +00:00

chore: fix job 769c2b1bd2

davide added 1 commit 2026-09-10 23:08:04 +00:00

chore: fix job a351a6bb24

davide added 1 commit 2026-09-10 23:10:53 +00:00

chore: fix job 7c97598eae

davide added 1 commit 2026-09-10 23:11:54 +00:00

chore: fix job 584dc0e944

davide added 1 commit 2026-09-11 07:41:19 +00:00

chore: try custom image 1ac93a2946

davide commented 2026-09-11 12:30:01 +00:00

Owner

• Copy link
• Copy Markdown

Waiting on https://code.forgejo.org/forgejo/runner/issues/1738 to make the forgejo entrypoint work in the action service.

Waiting on https://code.forgejo.org/forgejo/runner/issues/1738 to make the forgejo entrypoint work in the action service.

davide added 1 commit 2026-09-12 13:46:08 +00:00

Merge remote-tracking branch 'origin/main' into ci/add-test-workflow 713c86d423

Some checks failed

Hide checks

check-formatter.yaml / Checks with formatters (pull_request) Successful in 8s

Required

Details

check-prettier.yaml / Check files formatting (pull_request) Successful in 2s

Required

Details

check-linter.yaml / Checks with linters (pull_request) Successful in 17s

Required

Details

check-syntax.yaml / Checks with static tools (pull_request) Successful in 11s

Required

Details

check-test-unit.yaml / Run unit tests (pull_request) Successful in 9s

Details

check-yamllint.yaml / Lint yaml files (pull_request) Successful in 2s

Required

Details

check-test-integration.yaml / Run integration tests (pull_request) Failing after 16s

Details

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin "ci/add-test-workflow:ci/add-test-workflow"

git switch "ci/add-test-workflow"

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

  

Compat/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Abandoned

Somebody has started to work on this but abandoned work

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

No labels

Compat/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Security

Kind/Testing

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Abandoned

Status

Blocked

Status

Need More Info

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

projects/forgejo-agent!275

No description provided.