fix(ci): delete the per-branch push triggers instead of adding feat/** #6

2026-09-29T06:56:36Z

gitea-admin commented

2026-09-29 06:56:36 +00:00

The tracked next-step said "align gate.yml's push trigger with this repo's feat/**
prefix". Doing that literally would have made things worse, so this does the opposite.

act_runner runs at capacity 1. A branch push and its PR fire the same gate over the
same tree, and the redundant run serialises ahead of the PR run — doubling the wall
clock on the one result that gates the merge. Adding another prefix widens that problem.
infra/plex/claim-ship.sh currently has to pick a feat/ branch name specifically to
dodge this, during a loop racing a short-lived token.

The list also silently failed to match this repo's own convention — branches here are
feat/**, which was absent, so "fast feedback" never fired for the most common prefix.
Nobody noticed for a month, because the only symptom of a wrong entry is a missing run.
Any hand-maintained prefix list has that failure mode; deleting the list removes the class
rather than correcting one entry.

It was redundant anyway: CLAUDE.md already requires ./ci/gate.sh in the pinned toolbox
before pushing (74s locally), and the PR gate re-runs it authoritatively.

push: [main] is kept — post-merge main must still be verified, and it's the only run
for which no PR context exists.

Gate: PASS, rc 0, 74s.

Co-Authored-By: Claude Opus 5 (1M context) [email protected]

🤖 Generated with Claude Code

The tracked next-step said *"align `gate.yml`'s push trigger with this repo's `feat/**` prefix"*. **Doing that literally would have made things worse**, so this does the opposite. `act_runner` runs at **capacity 1**. A branch push and its PR fire the *same* gate over the *same* tree, and the redundant run **serialises ahead of the PR run** — doubling the wall clock on the one result that gates the merge. Adding another prefix widens that problem. `infra/plex/claim-ship.sh` currently has to pick a `feat/` branch name specifically to *dodge* this, during a loop racing a short-lived token. The list also silently failed to match this repo's own convention — branches here are `feat/**`, which was absent, so "fast feedback" never fired for the most common prefix. Nobody noticed for a month, because **the only symptom of a wrong entry is a missing run.** Any hand-maintained prefix list has that failure mode; deleting the list removes the class rather than correcting one entry. It was redundant anyway: `CLAUDE.md` already requires `./ci/gate.sh` in the pinned toolbox before pushing (74s locally), and the PR gate re-runs it authoritatively. `push: [main]` is **kept** — post-merge main must still be verified, and it's the only run for which no PR context exists. Gate: **PASS, rc 0, 74s**. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> 🤖 Generated with [Claude Code](https://claude.com/claude-code)

gitea-admin added 1 commit 2026-09-29 06:56:37 +00:00

fix(ci): delete the per-branch push triggers instead of adding feat/** to them

gate / gate (pull_request) Successful in 1m34s

Details

gate / conformance (pull_request) Has been skipped

Details

bf98a99af6

The tracked next-step said "align gate.yml's push trigger with this repo's feat/**
prefix". Doing that literally would have made things worse, so this does the opposite.

act_runner runs at capacity 1. A branch push and its PR fire the SAME gate over the SAME
tree, and the redundant run SERIALISES AHEAD of the PR run -- doubling the wall clock on
the one result that gates the merge. Adding another prefix widens that, it does not fix
it. infra/plex/claim-ship.sh currently has to pick a feat/ branch name specifically to
DODGE this, during a loop that is racing a short-lived token.

The prefix list also silently failed to match this repo's own convention: branches here
are feat/**, which was absent, so the "fast feedback" never fired for the most common
prefix. Nobody noticed for a month because the only symptom of a wrong entry is a MISSING
run. Any hand-maintained prefix list has that failure mode. Deleting the list removes the
whole class rather than correcting one entry.

It was redundant anyway: CLAUDE.md already requires ./ci/gate.sh in the pinned toolbox
before pushing (74s locally), and the PR gate re-runs it authoritatively.

push: [main] is KEPT -- post-merge main must still be verified, and it is the only run for
which no PR context exists.

FOLLOW-UP once this and #5 are both merged: the feat/ rationale in
infra/plex/claim-ship.sh becomes obsolete and its comment should be trimmed. The script
keeps working either way.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

jakman85 merged commit 67a54a33a4 into main

2026-09-29 07:22:20 +00:00

jakman85 referenced this issue from a commit

2026-09-29 07:22:22 +00:00

Merge pull request 'fix(ci): delete the per-branch push triggers instead of adding feat/**' (#6) from fix/gate-push-trigger-matches-feat-prefix into main

gitea-admin referenced this pull request

2026-09-29 07:30:30 +00:00

docs(ci): close out the hardening; correct a claim that shipped wrong #9

gitea-admin referenced this pull request

2026-09-29 20:35:08 +00:00

feat(ci): the pipeline is the approver #17

gitea-admin referenced this issue from a commit