Jarvis 5c7aaac955 ci: restrict push-event CI to protected branches (main) ...

Every feature-branch push currently fires TWO pipelines — a push CI and a
pull_request CI — doubling load on the storage-constrained (spinning-disk)
Woodpecker runner. The push run on feature branches is redundant; the PR
pipeline is the merge gate. Run push CI only on main; PR + manual CI still
run on every branch. ~halves feature-branch CI load, zero loss of gating
(branch protection requires no push/ci status context).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QDgorbfgN4Fgi1iHGkgndn

2026-07-12 17:19:24 -05:00

..

ci-image.yml

CI: add pre-baked ci-base image (producer) [Phase 1a] (#637)

2026-06-22 22:20:48 +00:00

ci.yml

ci: restrict push-event CI to protected branches (main)

2026-07-12 17:19:24 -05:00

publish.yml

chore(ci): bump ci-base image node 22 → 24-alpine (#639)

2026-06-23 00:59:39 +00:00