Since this could happen with a lot of services, maybe it would be worth a retry option? Especially if it's part of a pipeline.
It's a corporate one. We are also looking into options on Github's end.
Hi @<1545216070686609408:profile|EnthusiasticCow4> , it sure looks like a rate limit issue - are you using a free GitHub account or a paid one?
I know other services (GitLab, DockerHub etc.) also rate-limit, I assume it's the same case
After some digging we found it was actually caused by the routers IPS protection. I thought it would be strange for github to be throttling things at this scale.
Well, usually it's a matter of tier - I would assume adding a retry mechanism to bypass tier rate limit mechanisms in other services is a very nice thing to do 🙂