Skip to content

DO NOT MERGE TO DEV: chore(ci): retire the WIP-limit nudge (no-op tombstone, not a deletion) - #125

Merged
LukasWodka merged 3 commits into
developfrom
chore/retire-wip-limit
Aug 2, 2026
Merged

DO NOT MERGE TO DEV: chore(ci): retire the WIP-limit nudge (no-op tombstone, not a deletion)#125
LukasWodka merged 3 commits into
developfrom
chore/retire-wip-limit

Conversation

@LukasWodka

@LukasWodkaLukasWodka commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Retires the WIP-limit nudge org-wide. The kanban's Code review limit 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 mergedbackend#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#17

This 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:

branchrepos still carrying the caller
staging10 — all release-train repos
main / master14

A pull_request invokes the workflow on its base branch. Promotion PRs are based on staging and main/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_call signature, body replaced with a single notice. Every lingering caller stays green, the nudge stops everywhere the moment this reaches main, and there is no ordering hazard left to get wrong.

Delete the file for real once grep -r wip-limit-check across all branches of all repos comes back empty. The tombstone says so in its own header.

Also in this PR

  • Deletes .github's own caller (wip-limit-caller.yml) — this repo's copy, safe to remove outright.

Note

There was never an In progress WIP limit. The reusable only ever accepted status-name defaulting to "Code review" with limit: 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

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
@LukasWodkaLukasWodka self-assigned this Aug 2, 2026
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
@LukasWodkaLukasWodka changed the title chore(ci): retire the WIP-limit reusable — MERGE LAST, after all 15 callerschore(ci): retire the WIP-limit nudge (no-op tombstone, not a deletion)Aug 2, 2026
@LukasWodka
LukasWodka merged commit 74ffb7f into developAug 2, 2026
2 checks passed
@LukasWodkaLukasWodka changed the title chore(ci): retire the WIP-limit nudge (no-op tombstone, not a deletion)DO NOT MERGE TO DEV: chore(ci): retire the WIP-limit nudge (no-op tombstone, not a deletion)Aug 3, 2026
@LukasWodka
LukasWodka deleted the chore/retire-wip-limit branch August 14, 2026 13:53
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@LukasWodka