GitHub operations should handle rate limitting

[rwinch]

No description provided.

[mp911de]

I see two options: 1. show an error page with "come back later" (if facing the user) or use event sourcing so actions are not lost. That would play nicely also with headless operations if the Github hook is triggered but github-cla is not able to update the PR status because of rate limiting errors.

[Shredder121]

I think there is one more option.
3) Ask GitHub for a bigger quota on a key.

Or is that not a viable option? How much does the app exceed the regular quota?

[rwinch]

@Shredder121 Thanks for the response. We haven't yet run over the quota, but we have only rolled out to a few applications. We can ask for more quota, but of course we can always end up exceeding the new quota too.

[Shredder121]

Yes, I see.
I was just wondering if you already knew how much quota was needed.

There are some conditional requests that we could employ, but other than that it's mostly POSTs, so the best we can do is hold off requests until something changes (no unnecessary commit statuses, comments and the like).

Just wondering, how much has gone into conditional requests so far?

[rwinch]

Thanks for the reply. We could do conditional requests, but at that point we would still need to give an error to the user saying we cannot display it. To me the effort for this would probably not be worth it.