Happy holidays! Our organization has a private Jenkins setup in an intranet, so webhooks are not an option and we have to use polling to discover commits and PRs. Jobs are generally created via Jenkins Pipelines and Github Organization Folder technologies, so we told the Jenkins server once which GHO to scan (and then to check out code over SSH), and then it is all automatic. But as we have more and more components and branches and PRs to them, a limit arises…
While we’re trying to balance the frequency of polls vs. latency of CI, we sometimes hit the REST API quota of apparently 5000 points (the Jenkins plugins actually seem to implement a lower watermark internally as some “budget” that the scanning job exceeds while there are some 1000-2000GH points remaining, and I don’t know if they use caching requests, but that’s not a question for you I guess).
The question is whether our setup is eligible for a higher quota? According to https://developer.github.com/apps/building-github-apps/rate-limits-for-github-apps/ our reading was that having many collaborators and repo components in our organization (42ity) should have added 50 requests per hour for each to the quotas - but I don’t see it in practice. Does that note only apply to organizations with paid accounts?
Also, the documentation is not quite clear - does it add 50 pts for each of the total head/repo counts, or just for those above the base 20 items?