A review nobody can merge past
inline publishes a check run on every pull request head. Off, report only, or block at a severity you choose. A finding clears when its thread resolves or when a later push changes the code it flagged, so the gate opens on its own the moment the work is done.
It clears itself
when you fix it
No second bot command, no re-request. Resolve the thread or push the change and the check recomputes on the next event. Findings still unanswered stay listed, with what each one is waiting on.
- Idempotency key is written after the chargethread resolved
- Replay cache key omits the tenant idcode changed by 8f4c1ab
- Retry budget is never reset between attemptsawaiting a reply
The record
behind the check
Every check links back to the full review: what was found, what was suppressed and why, what the sandbox proved, and what the whole thing cost.
$0.312
88,402
61,180
9,744
1m 47s
This PR adds idempotency keys to the charge endpoint and a replay cache in front of it. The data model is right, but the key is persisted after the charge rather than before it, so concurrent retries can double charge; the replay cache is also keyed without the tenant id, which lets one tenant read another tenant's cached response.
Idempotency key is written after the charge, not before
Replay cache key omits the tenant id (IDOR)
Retry budget is never reset between attempts
Included
Put it on one repository
Connect GitHub, enable a repo, and the next pull request opened gets a review.