ci: restrict push-event CI to protected branches (halve feature-branch load) #721

Merged

jason.woltje merged 1 commits from fix/ci-push-protected-only into main

2026-07-12 22:48:59 +00:00

Author	SHA1	Message	Date
Jarvis	5c7aaac955	ci: restrict push-event CI to protected branches (main) All checks were successful ci/woodpecker/pr/ci Pipeline was successful Details 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

Author

SHA1

Message

Date

Jarvis

5c7aaac955

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

ci/woodpecker/pr/ci Pipeline was successful

Details

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: restrict push-event CI to protected branches (halve feature-branch load) #721

1 Commits