🔀 Workflows — CI Build workflow for the Todo repo #6

New issue

Open

opened 2026-09-28 07:56:05 +00:00 by SemianiakaVY · 0 comments

SemianiakaVY commented

2026-09-28 07:56:05 +00:00

Owner

Goal — keep the template's CI Build workflow alive for the Todo repo on Elsa Flows (/flows).

Owner — Elsa Workflows Manager (w4c-elsa).

Deliverables

The CI Build workflow definition imported/created on /flows, renamed to the Todo project ("Todo List CI") and running the stack's checks: install → lint → typecheck → test → build.
Its entry script aligned with this repository (.w4c/workflows/ci-build.yaml still carries the Online Shop name; the shell entry must match the pnpm commands of docs/PLAN.md §6).
The definition is published (a version exists) and a run is visible in its run history.

Acceptance (runtime)

Trigger a manual run on /flows: it finishes green against this repository, and a deliberately failing check is reported as failed — not as a silent success.

Ref — .w4c/workflows/ci-build.yaml, docs/PLAN.md §5–§6, /flows.

**Goal** — keep the template's CI Build workflow alive for the Todo repo on Elsa Flows (`/flows`). **Owner** — Elsa Workflows Manager (`w4c-elsa`). **Deliverables** - The CI Build workflow definition imported/created on `/flows`, renamed to the Todo project ("Todo List CI") and running the stack's checks: install → lint → typecheck → test → build. - Its entry script aligned with this repository (`.w4c/workflows/ci-build.yaml` still carries the Online Shop name; the shell entry must match the pnpm commands of `docs/PLAN.md` §6). - The definition is **published** (a version exists) and a run is visible in its run history. **Acceptance (runtime)** - Trigger a manual run on `/flows`: it finishes green against this repository, and a deliberately failing check is reported as failed — not as a silent success. **Ref** — `.w4c/workflows/ci-build.yaml`, `docs/PLAN.md` §5–§6, `/flows`.