> because all your Jenkins instances are - per the GitHub ToS - supposed to be using the same API Key
before reading this - I had always wondered if we could setup multiple GH "bot" accounts with keys to try parallelize things and work around this issue, but the ToS specifically says "You may not share API tokens to exceed GitHub's rate limitations.", so that idea is out I understand why they specify that, and it's a valid clause.
would it be possible to implement some form of log of the qty of each type of API call to GitHub (maybe by endpoint?) to see which areas of the usage are hurting the quotas the most? are there places where information can be cached to try cut down on API call volumes?
or to rephrase - should <someone> be trying to make the plugin's API call usage more lean and efficient as a solution to the root cause?