Uh oh!
There was an error while loading. Please reload this page.
DO NOT MERGE TO DEV: chore(ci): retire the WIP-limit nudge (no-op tombstone, not a deletion) - #125
Merged
Merged
Conversation
Removes the reusable itself. MUST land after every caller is gone: a caller pointing at a deleted reusable fails hard, turning a soft nudge into a red check on every PR in the fleet. Refs: tracebloc/backend#1405
Removes the reusable itself. MUST land after every caller is gone: a caller pointing at a deleted reusable fails hard, turning a soft nudge into a red check on every PR in the fleet. Refs: tracebloc/backend#1405
Deleting it would break every caller still present on staging and the prod branches - a caller pointing at a missing reusable fails hard. Measured 2026-08-02: the caller is still on staging in all 10 train repos and on the prod branch in 14. Those copies need a staging hop AND a prod hop to clear. A tombstone keeps them green and removes the ordering hazard entirely. Refs: tracebloc/backend#1405
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Retires the WIP-limit nudge org-wide. The kanban's
Code reviewlimit of 30 assumed a human-paced queue; the column now sits around 50 with items turning over in days, so the nudge fired on nearly every PR and carried no signal. A limit that is always exceeded is noise, not a limit.All 15 caller PRs are merged —
backend#1438·tracebloc-engine#566·client-runtime#254·averaging-service#276·frontend-app#731·data-ingestors#434·tracebloc-py-package#371·cli#446·design-system#103·client#535·docs#74·model-zoo#114·start-training#31·tracebloc-website#421·claude-skills#17This PR no longer deletes the reusable — and that is deliberate
The first version of this PR deleted
wip-limit-check.yml. That would have broken the release train's own promotion PRs in every repo.A workflow file lives on every branch it was ever merged into, and the caller was only removed from
develop. Measured 2026-08-02, after all 15 merges:stagingmain/masterA
pull_requestinvokes the workflow on its base branch. Promotion PRs are based onstagingandmain/master— precisely the branches that still have the caller. And a caller pointing at a deleted reusable does not degrade quietly: it fails hard, turning a soft comment into a red check.Those copies only clear after the deletion propagates through a staging hop and a prod hop — two full release cycles.
So this PR now makes the reusable a no-op tombstone: same
workflow_callsignature, body replaced with a single notice. Every lingering caller stays green, the nudge stops everywhere the moment this reachesmain, and there is no ordering hazard left to get wrong.Delete the file for real once
grep -r wip-limit-checkacross all branches of all repos comes back empty. The tombstone says so in its own header.Also in this PR
.github's own caller (wip-limit-caller.yml) — this repo's copy, safe to remove outright.Note
There was never an
In progressWIP limit. The reusable only ever acceptedstatus-namedefaulting to"Code review"withlimit: 30, and no caller overrode it. Nothing else to remove.Nothing gated on this — it never blocked a merge and no required status check is affected.
Refs: tracebloc/backend#1405
🤖 Generated with Claude Code