Top
Best
New

Posted by maxnoe 9 hours ago

Incident with Pull Requests, Issues, Git Operations and API Requests(www.githubstatus.com)
219 points | 174 commentspage 4
dist-epoch 9 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 8 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 8 hours ago||
Yes, on a single repo. Now multiply that per bazillion companies on github, some of which are trying that.
julianlam 8 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 7 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 8 hours ago|||
This seems odd to me. Why would you need to commit every second?
gedy 7 hours ago||
And push to remote as well? Seems not thought out
andyjohnson0 8 hours ago|||
> GitHub is not agent scale.

Is the scaling issue with git or github?

throwaway613746 7 hours ago||
[dead]
Arbortheus 9 hours ago||
Fed up and bored of this
hehe1 4 hours ago||
dthtrj
emartinez-dev 8 hours ago||
I thought it was the yesterday's thread but no, here we go again
shevy-java 6 hours ago||
I think it is time to decouple GitHub from Microsoft. Microsoft has shown irresponsible behaviour - and this continues. They keep on going at it until nothing works anymore. Typical microslop work.
pocksuppet 6 hours ago|
You don't get to control that. It is Microsoft's right to do whatever it wants with GitHub - it could shut down tomorrow, or demand face ID. If you want to control what happens with a thing, you have to make the thing instead of letting someone else make the thing and sell it to Microsoft.

Your choice is to accept the product that exists on the market, switch to another product that exists on the market (such as Codeberg or self-hosted Forgejo), make your own product, or not use any.

OkayPhysicist 4 hours ago||
You missed the option to "lobby the government to tell Microsoft to straighten up and fly right". Microsoft is a corporation, a legal entity only created with the permission and grace of the State of Washington.
pocksuppet 2 hours ago||
Sure, I guess skywriting prayers to the spaghetti monster is also an option, but neither of those will do anything.
rvz 9 hours ago||
Again?

It was just yesterday [0] that GA was down and another incident today? I am convinced that Copilot and Tay.ai are destroying GitHub and there is no CEO of GitHub to contact.

Now will you please self-host as I said 6 years ago? [1]

[0] https://news.ycombinator.com/item?id=48278635

[1] https://news.ycombinator.com/item?id=22867803

KptMarchewa 8 hours ago||
GitHub famously does not have a single 9 of uptime.
rob 9 hours ago||
You think a Microsoft chatbot from 2016 is destroying GitHub?
insider123 5 hours ago|||
Microsoft corporate culture destroys Github reputation and tech.
rvz 8 hours ago|||
At this point, you might as well say that is what's happening at GitHub with the help of GitHub Copilot since nothing has changed and has only gotten worse over time.