Why should this host (and presumably every similar host) take on the burden of this extra complexity?
Would a modicum of caching in GitHub Actions libraries not make this problem go away for all hosts in this category?
Would a modicum of caching in GitHub Actions libraries not make this problem go away for all hosts in this category?
I think a quite reasonable expectation from GitHub would be to have an all-of-GitHub-wide rate limit that CI can use for requests to any given site, and have jobs fail/delay if GitHub has exceeded that, and expect sites to explicitly opt in if they're fine with more than that rate. Would of course very much suck for GitHub CI users that want to pull from sites not opted in, but at least GitHub would stop offering free DDoS services.