Top
Best
New

Posted by maxnoe 8 hours ago

Incident with Pull Requests, Issues, Git Operations and API Requests(www.githubstatus.com)
213 points | 169 commentspage 3
fen4o 8 hours ago|
Tried to do a git push - it succeeded after 3 mins. Then I wanted to open a PR and it failed with a 500 error.

Facepalmed and decided that this is it for today.

looperhacks 8 hours ago||
Maybe we should start posting av story when GitHub has been fine for some time instead of posting every incident
trenchgun 4 hours ago||
But everything else still works fine, right?
cedws 8 hours ago||
I'm so done with GitHub.
maxnoe 8 hours ago||
GitHub Incident again/
denysvitali 8 hours ago|
At this point we can even stop specifying that it's GitHub...
abhashanand1501 7 hours ago||
as a github user, we are paying for the slow git operations through our github action minutes, if someone from GH is here, will you be compensating for it?
drcongo 8 hours ago||
For years we had a GitHub status thing in our Slack but I had to remove it about a year ago because the noise got too much, it would be unbearable in 2026.
Hamuko 8 hours ago||
Yesterday my CI runs wouldn't even be created because Actions was eating shit, and today my CI runs get created but fail because the API is eating shit. Fun.
dist-epoch 7 hours ago|
GitHub is not agent scale.

Multiple companies are trying to create new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo.

It's like switching from horse buggies to automobiles, the whole worlds needs re-architecturing to handle the new load.

The age of boutique hand-coding is being replaced by the age of industrial software factories.

swiftcoder 7 hours ago||
> new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo.

This is not a particularly novel level of scale. Facebook's mercurial backend had to handle >5,000 developers committing to the singular monorepo long before LLMs were a thing

KptMarchewa 7 hours ago||
Yes, on a single repo. Now multiply that per bazillion companies on github, some of which are trying that.
julianlam 7 hours ago|||
Why the heck would you want to do this. Using git as your undo chain sounds like a pretty awful thing to do.
dpkirchner 6 hours ago||
I think it'd be pretty neat to be able to rebase my undo history on to a remote branch someone else is working on.
skinfaxi 7 hours ago|||
This seems odd to me. Why would you need to commit every second?
gedy 6 hours ago||
And push to remote as well? Seems not thought out
andyjohnson0 7 hours ago|||
> GitHub is not agent scale.

Is the scaling issue with git or github?

throwaway613746 6 hours ago||
[dead]
More comments...