Rate limit

[kapcod]

On many changed files, PR, the action gets into a loop of rate limit errors.

Warning: [@octokit/plugin-throttling] `onAbuseLimit()` is deprecated and will be removed in a future release of `@octokit/plugin-throttling`, please use the `onSecondaryRateLimit` handler instead
{ name: 'octokit' }
Warning: Abuse limit hit with "POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews", retrying in 5 seconds.

It appears that 5-second retries are not sufficient for GitHub to release the rate limit.

My suggestion is to add a comment as soon as every file scan is finished, this way the delay between POSTs will be long enough not to cause this loop.

[anc95]

it does the way add a comment as soon as every file scan is finished now. how many file changes in your commit?

[kapcod]

130. And i didn't see any comment, but saw infinite loop of rate limit and retry messages. Unfortunately I've set a 30m timeout on whole job time so couldn't see of it would eventually succeed. But i assumed it buffers all the comments and shoots all together.

…

On Sun, Jan 4, 2026, 05:32 小安 ***@***.***> wrote: *anc95* left a comment (anc95/ChatGPT-CodeReview#201) <#201 (comment)> it does the way add a comment as soon as every file scan is finished now. how many file changes in your commit? — Reply to this email directly, view it on GitHub <#201 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHKEBSV63QWJWOM4DJWRHL4FCCVTAVCNFSM6AAAAACQH5EYWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBXGU4DKNJYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[anc95]

hi @kapcod
I was thinking about this for a while. there are two types of rate limit of Github (for your reference https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#about-secondary-rate-limits), the current implement may hit the secondary rate limit.

first, I need admitted that I said wrong in the first reply, I checked the code, the review only sent once after all files reviewed by GPT (using API https://docs.github.com/en/rest/pulls/reviews?apiVersion=2022-11-28#create-a-review-for-a-pull-request). the api body already contains all comments, so only sent one time, so, in theory, would not hit the primary rate limit.

but as for the secondary limit, there has limit on the content generation, it says

Create too much content on GitHub in a short amount of time. In general, no more than 80 content-generating requests per minute and no more than 500 content-generating requests per hour are allowed. Some endpoints have lower content creation limits. Content creation limits include actions taken on the GitHub web interface as well as via the REST API and GraphQL API.

These secondary rate limits are subject to change without notice. You may also encounter a secondary rate limit for undisclosed reasons.

in our case there has 130 files changed, the comment amount may more than 130 (if averagely there are two change chunks per file, then will have 260 comments need to be submitted), I think this might be tagged as abuse use by GitHub side.

[Br1an67]

I'd like to work on this. The fix batches review comments into smaller groups (default 40 per batch with 5s delay) to stay under GitHub's secondary rate limit for content-generating requests.

PR: #206