Live data from Hacker News

Incident with Pull Requests, Issues, Git Operations and API Requests

githubstatus.com

101–110 of 221 posts

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#101

Earlier quoted context omitted.

> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…

Compared to near unusable pages that large organizations produce, yes this page is highly effective at conveying information. Who cares how it was produced?

> this page is highly effective at conveying information

Is it though? If the page is near unreadable?

* Almost pure-black background rendering every not-pure-white colour barely readable

* Dark-grey and low saturation colours used almost everywhere, for both fonts and other coloured elements (the orange cells in the calendar are the most readable thing)

* Thin fonts - coupled with the dark grey colours this just adds to the readability issues

* Yet another incredibly long info-dump of a page

And then as far as actual information:

* Vanity metrics as the main information, that is a lot of things with no context or historical information

* A lot of aggregates and rollups that aren't that useful

No, I haven't tried Reader Mode.

It's a good demo for UI state syncing though, I'll give it that.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#102
post #6

https://isgithubcooked.com Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.

The UI of that page is so nice, should build a github competitor. The user profile / contributions and PR UX is pretty much the entire "hub" product since git is a fully separate offline app.

The UI is in the default claude code style

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#103
post #59

Earlier quoted context omitted.

> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…

The Bootstrap of 2020s.

At least Boostrap pages were readable ;)

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#104

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.

[dead]

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#105
post #78

If you go to www.githubstatus.com, the downtime is not showing in the chart. I was annoyed enough yesterday when I visited this page to figure out why my Actions had failed and was greeted with big green ticks and only a tiny red rectangle halfway down the page to indicate the problem. This time they've just scrubbed the evidence outright?

The "Git Operations" chart is showing all green, but several of the recent blocks have a note showing there was an outage.

Today's is green, even though there was an outage.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#106
post #26
post #6

https://isgithubcooked.com Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.

They are already cooked as this has been happening ever since the Microsoft acquisition and it was run to the ground before 2023. At this point you would get better uptime by just self-hosting your own GitLab, Forgejo or Codeberg instance instead of dealing with Github's unreliablity. There is no defending them with their clear neglet and carelessness of the platform.

I moved most of my projects off GitHub to Forgejo and will be using Tangled too for public repositories. I don’t think people realize that if you self host Forgejo, you get 99% of the functionality of GitHub with zero of the limitations. Especially if you have the hardware to spare for CI runners. And if self hosting isn’t your thing you can always just use Codeberg and Tangled directly.

I’m working on an open source Forgejo browser called Joui. It’s coming along nicely, and is so much snappier than GitHub in every single way.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#107
post #44

Earlier quoted context omitted.

> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…

What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.

Outside design systems I rarely get good CSS from LLMs.

3D type stuff too, it's useless outside boilerplate.

Very little spatial reasoning training, no end-user subjective reasoning inference (Google is starting to though even in unrelated chats), so it's no surprise the LLM doesn't know what you want.

Since I don't even know what I want half the time until I saw it, the subjective reasoning piece is key - that is, being able to predict what I'll want to pretty good accuracy. Then you have your agents etc.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#108

Earlier quoted context omitted.

> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…

Compared to near unusable pages that large organizations produce, yes this page is highly effective at conveying information. Who cares how it was produced?

A lot of software engineers do still care how software is produced. That's a good thing!

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#109

Earlier quoted context omitted.

How is it painful to use GitLab? Curious, as a user of both, I find them both nice. I like GitLab CI/CD more than I do GHA, but that's personal preference/bias more than anything objective.

Everything about their UI/UX screams of doing the bare minimum to check off a box on a feature list. It reminds me of Jira.

As a daily GitLab user, I'd say that would be the main criticism I could levy at it as well. It does feel like there are a number of "and the kitchen sink" type features that are just there to check a box in a RFP or something.

That said, are the majority of people actually even _using_ those features? For us we're essentially just using GitLab for git, merge requests, and CI pipelines. A couple places we use the static page hosting. (First thing I do whenever I create a new repository is go into the settings and just uncheck _all_ the boxes.)

All of that core functionality works really well and is more than polished enough from my point of view.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#110

Earlier quoted context omitted.

GH was acquired by microsoft some eight years ago. It has been working quite well until recently. People may have had complaints about functionality, features, commercial issues, but the thing used to at least have a decent uptime until recently.

> It has been working quite well until recently. I'm not sure how reliable the data is, but average uptime seems to have dipped measurably starting within a year of the aquisition, according to https://damrnelson.github.io/github-historical-uptime/

They moved to Azure. Nothing improves on Azure.
Post reply on HN