-
|
Hey everyone, Iβm running into a recurring issue with GitHub API rate limits. About once or twice a day, I get blocked for 15β20 minutes, which interrupts my workflow quite a bit. Has anyone dealt with this before? Iβd love to hear any practical tips or workarounds to avoid hitting the limit so quickly. Some context:
Questions:
Any ideas, experiences, or suggestions would be greatly appreciated! Thanks π |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
One option, especially for CI is to use GitHub App authentication, that has 15k/h limit. In general, I could recommend splitting state into smaller pieces and leveraging remote_state to access data between them. We've separated resources that need to change rarely into multiple states, thus reducing the rate cost of execution drastically. |
Beta Was this translation helpful? Give feedback.
-
|
In this case, you can use "github_organization" to get all users instead of "github_user" for every username. |
Beta Was this translation helpful? Give feedback.
In this case, you can use "github_organization" to get all users instead of "github_user" for every username.