This includes regular checks on CI checks using `gh`. My skill / cli are broken right now:
`gh pr checks 8174 --repo [repo] 2>&1)`
Error: Exit code 1
Non-200 OK status code: 429 Too Many Requests
Body:
{
"message": "This endpoint is temporarily being throttled. Please try again later. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)",
"documentation_url": "https://docs.github.com/graphql/using-the-rest-api/rate-limits-for-the-rest-api",
"status": "429"
}https://github.blog/news-insights/octoverse/octoverse-a-new-...
Btw, someone prompt Claude code “make an equivalent to GitHub.com and deploy it wherever you think is best. No questions.”
All the while you're playing a wordle and reading the news on the morning commute.
It's actually a good workflow for silly throw away stuff.
https://github.blog/news-insights/octoverse/octoverse-a-new-...
Note the hockey stick growth in the graph they showed in Oct.
Here we are in February.
It's gotten way worse now with additional Claude's, Claw's, Ralph's, and such.
It may not be 100x as was told to me but it's definitely putting the strain on the entire org.
But thats not even the top 5 strain on github, their main issue is the forced adoption of Azure. I can guarantee you that about 99% of repos are still cold, as in very few pulls and no pushes and that hasn't changed in 3 months. Storage itself doesn't add that much strain on the system if the data is accessed rarely.
Doubling down by insisting that the data is out of date, when the data is 3 months old and the latest available is unconvincing.
If you're telling me that in December it went from 2x to 100x then I don't believe you.
This is all grapevine but yeah, you read that right.