You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the 500 / hour limit is something people who create lots of content hit regularly. We should definitely point that one out and consider to implement a more gracious handling of it, as folks will regularly hit it after ~25 minutes and will then need to wait for ~35 minutes before the script can resume. If they are aware of that limitations they might take it into account from the get go
The text was updated successfully, but these errors were encountered:
I just found out about https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api. There is a lot of additional information that will be relevant for folks hitting secondary rate limits that was not communicated previously here: https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#about-secondary-rate-limits
I think the 500 / hour limit is something people who create lots of content hit regularly. We should definitely point that one out and consider to implement a more gracious handling of it, as folks will regularly hit it after ~25 minutes and will then need to wait for ~35 minutes before the script can resume. If they are aware of that limitations they might take it into account from the get go
The text was updated successfully, but these errors were encountered: