Live data from Hacker News

An update on GitHub availability

github.blog

71–80 of 266 posts

Re: An update on GitHub availability

#71

Not enough attention is being put in the production/delivery mismatch. GitHub is claiming they require 30x scale due to the giant increase in repository creation, PRs, commits, etc. I have not seen a single product increase in features or quality as an end user, nor new significant products have come out in this period (other than the LLMs themselves). Where is all this code going?

I for one believe Microsoft when they say this code is going to Github... to die.

Half of my friends is vibe-coding something but they can barely get the rest of the group chat to use it once.

In companies, I see people vibe-coding "miracle apps" that fall under the smallest amount of scrutiny.

Basically people are doing the same developers do when they say "I can do this in a weekend", which is getting a prototype sort of running and then immediately losing energy (or in this case lacking ability) to push it forward.

Re: An update on GitHub availability

#72
Ruby catching strays

Good chuckle out of this post, it’s crazy that neither Atlassian (Bitbucket) or Gitlab are capturing value out of this same agentic coding boom. I wish github was separately publicly traded outside of Microsoft.

Nowhere to get exposure to this

Re: An update on GitHub availability

#73

anyone who's actually worked there, could you explain why they're finding scalability and reliability so hard? naively it seems like 'repo groups', ie clusters of repositories linked by being mutual forks, would be fairly isolated for the whole git storage layer, and everything else feels pretty easily parallelisable (issues, actions, etc, modulo taking locks now and then to submit results or whatever). and given tha…

recently there was a twit how GitHub PR diffs had 10 React components PER LINE. And how they optimized that to only 2 React components per line or something. > To summarize, for every v1 diff line there would be: > - Minimum of 10-15 DOM tree elements > - Minimum of 8-13 React Components > - Minimum of 20 React Event Handlers > - Lots of small re-usable React Components https://github.blog/engineering/architecture-op…

I'm asking about the infrastructure, obviously they chose for some reason to make my computer fans turn on to show some red and green lines on a text file.

Re: An update on GitHub availability

#74
GitHub stability has been bad for me. And recently even the data they show me in the web has been unreliably.

Since yesterday, me and several colleagues noticed that the pull request lists on the website are incomplete, across many repositories. For example, on https://github.com/gap-system/gap/pulls it says "Pull requests 78" in the "tab list", but the PR list view reports "35 open" (the number 78 is correct, and confirmed by e.g. `gh pr list`)

And that despite https://www.githubstatus.com> reporting "all systems operational".

Re: An update on GitHub availability

#75

Earlier quoted context omitted.

Seems pretty sensible to not rely on a single provider for their large complex system?

I mean, amazon (shopping, along with prime video e.t.c.) runs on AWS.

When I was at AWS, retail was not yet running on AWS. Has that changed?

Prime video does use some AWS services, but live and on-demand are two entirely different beasts.

Re: An update on GitHub availability

#76
post #53

This latest incident was the nail in the coffin for me. I've been on GitHub since 2012 but I'm feeling the pull to migrate out to Gitea/Forgejo. Has anybody done this recently? How'd it go?

I moved over back when GitHub was planning to charge per minute to use my own runner. It was easy with Claude, the gh API, and forgejo web API. I even set up daily backups to my S3 clone of choice.

The only repos I left on GitHub are forks and one with a bit of public engagement.

Re: An update on GitHub availability

#77
post #26
post #13

It's kind of hard to read this with a straight face. The unlabelled graph with big numbers on top, the priorities that don't match with what we're experiencing, and a list of things that they're doing without a real acknowledgement of the _dire_ uptime over the last 12 months....

More numbers: https://x.com/kdaigle/status/2040164759836778878 What's the question here, you don't believe growth is currently exponential, or do you think it shouldn't be hard to scale, when 10x YoY is not enough?

These numbers should have been in the blog post, not the graphs that are present.

> What's the question here, you don't believe growth is currently exponential, or do you think it shouldn't be hard to scale

I think you're putting words in my mouth here; I didn't say either of those things. I'm saying that this blog post is a meaningless platitude when the github stability issues predate this, and that all this post says is "we hear you're having issues".

Re: An update on GitHub availability

#78

Earlier quoted context omitted.

But, there are? I can host a repo on GitHub, Codeberg and self host it too. Then I need to watch over main to keep it consistent between those. After that's established, I can do updates from wherever. Link'em in the README.

There are distributed forges? Yes, git is distributed, but often everything around it isn't. The case parent is trying to make, is that the rest ("federated forges") should also be distributed, not just git.

Ok, gotcha. So there's a demand for the additional features that are not bundled within git to be federated somehow.

I'd say we have emails, mailing lists and bug trackers. Or maybe: what is the missing killer feature that needs federation?

Post reply on HN