As a repomountie contributor,
I want to spread API requests to GitHub API
So that repomountie avoid hitting the GitHub API 1,000 search results limit and failing to collect necessary repository data.
Implementation Details:
The bot is a victim of its own success. When it starts, it gets a list of existing repositories, and goes through to see if any are non-compliant. To do this it needs to make quite a few API calls. This quickly hits the limit of API requests with GitHub.
I just added a user story above the issue body I think captures that to help with handing over the project and showing the backlog, we can add in a template to help with that
As a
repomountie
contributor, I want to spread API requests to GitHub API So thatrepomountie
avoid hitting the GitHub API 1,000 search results limit and failing to collect necessary repository data.Implementation Details:
The bot is a victim of its own success. When it starts, it gets a list of existing repositories, and goes through to see if any are non-compliant. To do this it needs to make quite a few API calls. This quickly hits the limit of API requests with GitHub.
https://docs.github.com/en/rest/reference/search#rate-limit https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting
Would be good spread this out over a longer period of time so it does not choke and nothing gets missed.
I've explained to Alec. Can add context if needed.