91–100 of 298 posts
Earlier quoted context omitted.
Over 100x is what I’m hearing. Though that could just be panic and they don’t know the real number because they can’t handle the traffic.
One hundred ? Did I read that right?
This is all grapevine but yeah, you read that right.
It would be interesting to have a graph showing AI adoption in coding against the number of weekly outages across different companies. I am sure they are quite correlated.
Earlier quoted context omitted.
How much has the volume increased, from what you know?
Over 100x is what I’m hearing. Though that could just be panic and they don’t know the real number because they can’t handle the traffic.
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"
}Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…
Earlier quoted context omitted.
The trend of "non-functional software" is happening everywhere. See the recent articles about Copilot in Notepad, failing to start because you aren't signed in with your Microsoft Account. We are in a future that nobody wanted.
> We are in a future that nobody wanted. Nor deserved.
[dupe] Discussion: https://news.ycombinator.com/item?id=46946827
[dupe] Discussion: https://news.ycombinator.com/item?id=46946827
The history for today is a bit of a mess really: https://www.githubstatus.com/history
Everyday you opt in to get wrecked by Microsoft.
You all do realize you all could, for a change, learn something and never again touch anything Microsoft related?
Fool me once...
They were talking about prioritizing migration into Azure for a long while now. Not sure this incident today is related. https://thenewstack.io/github-will-prioritize-migrating-to-a... And coincidentally, an early CircleCI engineer wrote an article about GitHub Action (TLDR: don't use GitHub Action for CI/CD!) https://www.iankduncan.com/engineering/2026-02-05-github-act... https://news.ycombinator.com/item?id=4690849…
You should reach the same conclusion by trying to use it for this purpose, but also indeed for any purpose at all. Incidents that make you unable to deploy making all your CD efforts pointless are only the cherry on top.
Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…