Github abuse rate limit error
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
For repos with a lot of commits/pull-requests, the release process fails with:
```
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/releases/latest, retrying in 1m.
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/issues/{issue_number}, retrying in 1m.
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/issues/{issue_number}, retrying in 1m.
✖ error Went over abuse rate limit GET /repos/{owner}/{repo}/issues/{issue_number}, retrying in 1m.
```
**Expected behavior**
Release process should not break.
**Environment information:**
```txt
v11.1.6
```
**Additional context**
This seems to be a secondary rate limit error. I don't see any prior log messages like `Request quota exhausted...`.
[octokit/plugin-throttling](https://github.com/octokit/plugin-throttling.js#readme) has a `fallbackSecondaryRateRetryAfter` configuration option. Perhaps that could be exposed also in the `auto` configuration so that I could increase it?
Alternatively we could upgrade `@octokit/plugin-throttling` to `>=v5.2.3`, [because the rate limit was increased from 5 to 60](https://github.com/octokit/plugin-throttling.js/commit/5335870a005c9dafc3280f221e89bac9d8fab361).
Update: The upgrade seems to be the way to go, because not only was the rate limit increased, also the implementation was improved.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.