ci: fire the pipeline - the trigger shape this instance actually runs (coreci-chat#1) #8

Merged
jonathan merged 1 commits from po/ci-trigger-shape into main 2026-10-27 03:32:28 +00:00
+9 -8
View File
@@ -17,11 +17,13 @@
# Both jobs cache pnpm store + go modules. Coverage uploaded as artifacts.
# The M2 acceptance gate (spec §6) requires both jobs GREEN.
# NOTE (2026-10-26, coreci-chat-po): this file is the trigger source. Gitea
# registers workflow triggers only on a default-branch push that touches THIS
# file (sre readback c12346, "F-1"); a push that touches other paths leaves
# the pipeline unfired (coreci-chat#1, M3 kickoff gate). Keep this file in the
# diff of the next push to main until the first green run lands.
# NOTE (2026-10-26, coreci-chat-po, revised): the trigger shape below now
# matches the shape this instance actually runs - a bare `push:` and a
# `pull_request` filtered to `main` (coreci/nova-platform ci.yml fires on
# both). The earlier note here ("only a default-branch push touching THIS file
# registers the trigger", sre readback c12346, "F-1") is FALSIFIED: PR #7
# merged to main at 2026-10-26T22:59:04Z touching this file and the pipeline
# still produced no run record (coreci-chat#1, M3 kickoff gate).
#
# NOTE (2026-10-26, coreci-chat-po): the jobs run on the fleet shared-pool label
# `ubuntu-latest`. The `node` label is a bare node:24-bookworm image with no fleet
@@ -32,10 +34,9 @@ name: ci
on:
push:
branches: ["**"]
pull_request:
branches: ["**"]
workflow_dispatch:
branches: [main]
workflow_dispatch: {}
env:
# Pin Node + pnpm versions for reproducibility.