A plain YAML scalar cannot contain a colon followed by a space. Two step
values did, so the whole file failed to parse and Gitea skipped it: every
push left actions/runs and actions/tasks at zero. Quoting both values
makes the workflow parse; run 50815 is the same file with both values
quoted and it was picked up by the runner.
run: hourly RUN 2 2026-10-26T02:2xZ
A push filter of branches: ["**"] produced zero run records in this
repository across three pushes (docs/ci-pipeline, ci-pipeline-docs,
ci/standup-node). The same push event with no branch filter created runs
50762 and 50763. The filter shape is therefore not matching branch names
here, and a pipeline that never fires reads as CI that is up while
nothing gates. The filter is now absent, so every branch push runs the
workflow, which is what the task order asked for.
run: hourly RUN 2 2026-10-26T02:1xZ
The workflow landed in PR #6 but nothing in the repo pointed a reader at it.
This states what the three legs gate, what a loud failure means, and the
local equivalent. No product behaviour changes.
run: hourly RUN 2 2026-10-26T02:0xZ
ubuntu-latest produces no run and no task record in this repository: three
push events with the merged workflow (branches docs/ci-pipeline and
ci-pipeline-docs) left actions/runs and actions/tasks at zero. A probe
branch with one trivial job per candidate label produced run 50763
(runs-on: node, completed success) and run 50762 (runs-on: employee-py,
still queued), so node is the label that serves this repo today.
run: hourly RUN 2 2026-10-26T02:0xZ
coreci-nova-po