Design CI workflow skeleton (GitHub Actions / Forgejo Actions) #48

New issue

Closed

opened 2026-07-31 19:42:02 +00:00 by Mark · 0 comments

Mark commented

2026-07-31 19:42:02 +00:00

Owner

Source: kanban task t_251e4b6c

Scope

Create the baseline CI workflow file(s) for this repo targeting both push and pull_request events.

Approach

Inspect repo to detect language/runtime (TypeScript/Node.js/Next.js) and existing scripts in package.json.
Author a workflow that runs install, lint, type-check, and test jobs in parallel where possible.
Cache npm dependencies keyed on package-lock.json hash.
Pin action SHAs, not tags.

Acceptance

Workflow file committed under .gitea/workflows/ci.yml (Forgejo Actions) and optionally .github/workflows/ci.yml (GitHub Actions).
Pushes trigger a green run on the current main HEAD.
PR template/checklist references the CI status.
Short summary in the PR body listing the jobs and their purpose.

Source: kanban task t_251e4b6c ## Scope Create the baseline CI workflow file(s) for this repo targeting both `push` and `pull_request` events. ## Approach 1. Inspect repo to detect language/runtime (TypeScript/Node.js/Next.js) and existing scripts in package.json. 2. Author a workflow that runs install, lint, type-check, and test jobs in parallel where possible. 3. Cache npm dependencies keyed on package-lock.json hash. 4. Pin action SHAs, not tags. ## Acceptance - Workflow file committed under `.gitea/workflows/ci.yml` (Forgejo Actions) and optionally `.github/workflows/ci.yml` (GitHub Actions). - Pushes trigger a green run on the current main HEAD. - PR template/checklist references the CI status. - Short summary in the PR body listing the jobs and their purpose.