Rate Limit GitHub on deployment

[martinratinaud]

When a deployment happens, it can happen that the rate limit for GitHub is reached.

Default server-to-server rate limits for GitHub.com
GitHub Apps making server-to-server requests use the installation's minimum rate limit of 5,000 requests per hour. If an application is installed on an organization with more than 20 users, the application receives another 50 requests per hour for each user. Installations that have more than 20 repositories receive another 50 requests per hour for each repository. The maximum rate limit for an installation is 12,500 requests per hour.

Server-to-server rate limits for GitHub Enterprise Cloud
GitHub Apps that are installed on an organization within an enterprise on GitHub.com are subject to a limit of 15,000 requests per hour per organization that has installed the app.

So several options:

• rework the error workflow to use fewer api calls
• Subscribe to GitHub Enterprise Cloud
• Ask the GitHub community if the rate can be increased on a project like Open Terms Archive

[martinratinaud]

Main problem is is that a declaration modification PR merged will trigger a deploy.

When this happens a lot (as it has been the past days, cleaning the contrib collection), the rate limit of GitHub API is touched, causing numerous alert emails to be sent.

As discussed with @MattiSG, here is a proposal PR #992 that will bypass this problem.

What this will do is the following

• ota track will track the changes
• ota track --schedule will track the changes only on scheduled run (and not on first run as it was before)