mirror of
https://github.com/MHSanaei/3x-ui.git
synced 2026-09-04 01:17:15 +00:00
Sanaei
25d0c06f89
Ten review runs fired in under two hours on 3 September and every one after 11:25 came back rejected: the five-hour usage window was at 100 percent (overageStatus rejected, org_level_disabled) while the seven-day window sat at 29. Two of them reviewed the same head SHA and one pull request was reviewed four times, because a draft/ready toggle re-fires pull_request_target and the skip decision is only reachable after a full checkout and a model boot. Settle it in the workflow instead: a bot comment carrying "Reviewed head:" and the pinned SHA means this head is done, so the pr-head checkout, the brief and the action are all skipped. An explicit "@claude review" is exempt, so a maintainer can still force one. A refused run also failed the job twice over - the action's exit 1 plus "the review posted nothing" - with nothing on the pull request to say why, which reads as a broken bot rather than an exhausted budget. The job now classifies its own transcript: a rejected rate_limit_event, or a 529 that survived every retry, posts one line on the pull request and stays green. Anything else still fails loudly. Also tightens that check, which counted ANY bot comment quoting the head SHA as a legitimate skip; the conflict-resolution job quotes SHAs too, so a dead run could go green on one.