matt/mailship
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Run checks in CI via Forgejo Actions #12

Merged
matt merged 1 commit from mailship-e77-run-checks-in-ci-via-forgejo-actions-605 into main 2026-09-14 20:00:59 +00:00
Conversation 0 Commits 1 Files changed 1 +31
hudson commented 2026-09-14 17:41:16 +00:00
Collaborator
Copy link

mailship-e77

Add a Forgejo Actions workflow so CI runs the repo's own check gate on every push and pull request. This keeps local, CI, and fragua execution in sync — ./script/checks is the single source of truth.

Changes

  • .forgejo/workflows/ci.yml — new workflow with one job (checks) running on ubuntu-latest. Steps: checkout, setup-node (reading .nvmrc), corepack + pnpm i --frozen-lockfile, then ./script/checks.
  • Triggers: push to main + pull_request. Concurrency group is workflow+ref with cancel-in-progress: true.

How to test

Push this branch to the Forgejo remote — the workflow must appear in the repo's Actions tab and run green. If the runner doesn't recognise ubuntu-latest, update the runs-on label to match the registered runner config before merging.

mailship-e77 Add a Forgejo Actions workflow so CI runs the repo's own check gate on every push and pull request. This keeps local, CI, and fragua execution in sync — `./script/checks` is the single source of truth. ## Changes - **`.forgejo/workflows/ci.yml`** — new workflow with one job (`checks`) running on `ubuntu-latest`. Steps: checkout, setup-node (reading `.nvmrc`), corepack + `pnpm i --frozen-lockfile`, then `./script/checks`. - Triggers: `push` to `main` + `pull_request`. Concurrency group is workflow+ref with `cancel-in-progress: true`. ## How to test Push this branch to the Forgejo remote — the workflow must appear in the repo's Actions tab and run green. If the runner doesn't recognise `ubuntu-latest`, update the `runs-on` label to match the registered runner config before merging.
hudson added 1 commit 2026-09-14 17:41:16 +00:00
feat(ci): add Forgejo Actions workflow for CI checks
All checks were successful
CI / checks (pull_request) Successful in 32s
Details
53b0182c7b 
Creates .forgejo/workflows/ci.yml that runs the repo's single-source-of-truth
check gate (./script/checks) on every push to main and every pull request.

Triggers: push to main, pull_request
Concurrency: group by workflow+ref, cancel-in-progress true
Steps: actions/checkout@v4, actions/setup-node@v4 (node-version-file: .nvmrc),
corepack + pnpm i --frozen-lockfile, then ./script/checks.

Part of bead mailship-e77.
matt approved these changes 2026-09-14 20:00:56 +00:00
matt merged commit c4b1a3fb4c into main 2026-09-14 20:00:59 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
matt
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
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: matt/mailship#12
No description provided.
Delete branch "mailship-e77-run-checks-in-ci-via-forgejo-actions-605"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?