fix(ci): bind Noema continuation to the next retry attempt - #2488
seonghobae wants to merge 1 commit into
Conversation
|
Warning Review limit reachedNext included review available in 7 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Exact-head admission correction — Ready is review admission only. Fresh audit against base
This PR is moved to Draft/Proposed until the causal owner repair is present on a successor exact head and re-audited. Queued/pending work is neither an additional blocker nor passing evidence. No Close, force push, destructive rebase, manual rerun, synthetic status/approval, merge, auto-merge, or bypass was performed. |
Summary
Bind each Noema 429 continuation to the immediately preceding retry attempt. A stale or malformed transition fails before dispatch, while attempts 0→1 and 1→2 remain valid.
This carries the remaining valid transition guard from #2371 onto the current central-dispatch workflow. The older PR's product-repository dispatch target is obsolete: the current workflow sends to the central
.githubhandler and checks the exact live PR head and base.Verification
GITHUB_ACTIONS=trueexecutable continuation test passed.actionlint .github/workflows/noema-review.ymlandgit diff --checkpassed.Hosted current-head review, required checks, and merge remain pending.