ci(2396): give .github its own customer-priority-bump caller, ahead of the flip (backend#2396) - #316
Conversation
…f the flip (backend#2396) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit e0e3179. Configure here.
saqlainsyed007
left a comment
There was a problem hiding this comment.
Reviewed — approving. A correct thin caller for .github's own customer-priority-bump: named -caller.yml because customer-priority-bump.yml in this repo is the reusable itself (matching the repo's <name>/<name>-caller pairing throughout), secrets: inherit, no inputs (all four defaulted) and no permissions: block — matching the callee and the 16 working callers. Shipping ahead of the exempt→required flip is forced, not preferred (bundling the flip would fail MISSING required caller on its own PR since the audit reads the caller off develop, which won't have it until merge — the #307 deadlock). The transient red audit between this merge and the follow-up flip is documented and is the cost of the land-caller-first rule, not a defect in this file. Green: checks pass, no open threads.
Wires this repo to the
customer-priority-bump.ymlreusable — the last of the threethat were never wired (
release-train#117andrfcs#47are the others).Why now
.github#313(backend#2348) added a second job to that reusable,bug-to-ready, whichmoves a
work-type:bugissue's card fromBacklogtoReady. Without a caller, a bugfiled here still lands in
Backlog— the refinement queue nobody pulls from — andorg-standards.mdcurrently carries a sentence naming these three repos as theexception.
The exemption's stated blocker has expired. The anchor
customer_priority_bump_caller_missingcitesbackend#1408 P3— "three dead inputs andhard-codes the
prioritylabel". Measured 2026-08-23:trigger-label×1,bug-label×2,project-number×1,org×1priorityNamed
-caller.yml, and that is not cosmeticcustomer-priority-bump.ymlin this repo is the reusable. A caller under the samename would overwrite the thing it calls. This repo pairs
<name>.ymlwith<name>-caller.ymlthroughout — stale-backlog, set-pr-status, fr-gate,advance-deploy-env, code-quality, fr-pass-comment, kanban-closure.
This ships ahead of the flip, and there is a red window
The
repo-inventory.ymlrow staysexemptuntil a separate, later PR flips it. Thatsplit is forced, not preferred — the same deadlock
#307documented for the stale sweep:the audit reads caller presence from the audited branch over the API, so this
repo's caller does not exist on
developuntil this merges, and bundling the flip wouldfail
MISSING required calleron its own PR forever becausegateis required.Known transient:
exemptplus a caller on the audited branch is itself a finding(
caller-drift.py:2260), so this repo's audit goes red between this merge and theflip — and while it is red, every other GUARDED-file PR is blocked. Suggested order:
release-train#117andrfcs#47(no effect on this repo's audit).github#306— already open and waiting on a green audit; land it firstNo inputs, no
permissions:blockMatching all 16 working callers and the callee, which declares neither. Every input
is defaulted, and a grant narrower than the callee needs fails the run at startup with
no jobs.
Verification
Not "this merged". The first
work-type:bugissue filed here afterwards landing inReadyuntouched. The caller pins@main, so this also depends onbug-to-readyhavingbeen promoted to
.github'smain.Part of tracebloc/backend#2396 — not
Closes, since the ticket also covers the twosibling callers and the inventory flip.
Note
Medium Risk
Inherits secrets and will auto-label issues and move kanban cards. Also opens a known audit-red window that blocks other GUARDED-file PRs until the follow-up inventory flip.
Overview
Adds a thin
customer-priority-bump-caller.ymlso this repo finally invokes the existing reusable onissues: labeled. Bugs labeledwork-type:bugcan move fromBacklogtoReady, andfrom:customerstill gets the binaryprioritylabel.Named
-caller.ymlbecausecustomer-priority-bump.ymlis the reusable in this repo. No inputs orpermissions:block; defaults andsecrets: inheritmatch the other working callers.Does not flip inventory from
exempttorequired. That must land in a follow-up immediately after, because merging this alone makesexempt+ caller a known audit finding and will block other GUARDED-file PRs until the flip.Reviewed by Cursor Bugbot for commit e0e3179. Bugbot is set up for automated code reviews on this repo. Configure here.