Take the pure rate-limit/jitter calculator (companion wave-1 issue) and actually wire it into the Governor chokepoint so a miner cannot burst writes past a per-repo or global cadence — both to respect GitHub's own rate limits and to prevent a runaway loop from flooding a repo with PRs/comments. This is the enforcement half — the underlying calculator is already contributor-built and tested; this issue is its enforcement wiring. Open, scored contributor work, provided the tests below (burst-throttling, global+per-repo buckets, window reset) are thorough.
Deliverables
References
- The pure rate-limit/jitter calculator (companion wave-1 foundation issue) — this issue is its enforcement wiring
src/auth/rate-limit.ts — the server-side vocabulary this local enforcement mirrors
- The Governor chokepoint (companion maintainer issue) — this is one of the calculators it composes
Take the pure rate-limit/jitter calculator (companion wave-1 issue) and actually wire it into the Governor chokepoint so a miner cannot burst writes past a per-repo or global cadence — both to respect GitHub's own rate limits and to prevent a runaway loop from flooding a repo with PRs/comments. This is the enforcement half — the underlying calculator is already contributor-built and tested; this issue is its enforcement wiring. Open, scored contributor work, provided the tests below (burst-throttling, global+per-repo buckets, window reset) are thorough.
Deliverables
evaluateLocalRateLimitper write-action-class + per-repo bucket before allowing executionjitteredBackoffMsrather than either failing permanently or busy-loopingReferences
src/auth/rate-limit.ts— the server-side vocabulary this local enforcement mirrors