Live data from Hacker News

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

githubstatus.com

141–150 of 221 posts

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

#141
post #44

Earlier quoted context omitted.

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.

Here is a provocative thought - maybe these are the so-called "better designs" from LLMs? It's not like writing English sentences is some huge secret you are sitting on that no one else knows.

> It's not like writing English sentences is some huge secret you are sitting on that no one else knows.

I'd actually say what really makes an excellent engineer stick out among many great engineers, is their ability to communicate clearly and knowing what needs to be communicated vs not, basically being way better at language and communication in general, and they also understand the important of it.

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

#142
post #129

Earlier quoted context omitted.

May has been filled with critical issues. It seems it's getting worse over time.

Commits are up 14x year-over-year https://x.com/kdaigle/status/2040164759836778878

Not a valid excuse without knowing what their historical growth rate has been. And how much of the instability is load related.

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

#143

Earlier quoted context omitted.

It's so unfortunate that Gitlab is a complete mess, that GitHub has no real competition now. I can only think that few months to a year from now there will be _something_ that works on an enterprise scale.

Have you forgotten about Azure Dev Ops aka Visual Studio Team System aka Team Foundation Server*? Yes, it's still Microsoft, but they've forgotten about it, so it runs entirely adequately and is actually a surprisingly okay github replacement. It does nothing special, but it does do everything, just in a way you often would rather it wouldn't. It doesn't have the flexibility of JIRA for the ticketing, and the deploym…

Only alternative outside of GitHub and GitLab I've used was Bitbucket, and it was worse - but this was time when GitHub was good.

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

#144
post #80

Earlier quoted context omitted.

It's fascinating how fast the Forgejo I host at my university's laboratory loads from my home network. Every page load is <100ms. I think it goes to show how much bloat we don't realise exists in modern webapps.

GitHub used to be like that before they rebuilt everything in React.

No, they didn’t rebuilt everything in React and current sluggishness of page loads is not related to React.

See: https://news.ycombinator.com/item?id=47940456

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

#145

Earlier quoted context omitted.

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.

I’m actively working on an alternative Frontend for Forgejo at the moment, completely self hostable, free, and open source. Moving everything from GitHub to Forgejo and Tangled for now. These outages haven’t effected me for the past month because of this.

Can you elaborate on how your Forgejo frontend will be different than the default one? I'm asking because I've only ever used GitHub, GitLab and Forgejo for longer periods and Forgejo was the fastest and easiest to use for me.

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

#146
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.

It's not physically possible to run post-mortems for issues at those rates. They should install OpenClaw for that as well.

AI: The cause of, and solution to, all of your tech debt.

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

#147

Earlier quoted context omitted.

Have you forgotten about Azure Dev Ops aka Visual Studio Team System aka Team Foundation Server*? Yes, it's still Microsoft, but they've forgotten about it, so it runs entirely adequately and is actually a surprisingly okay github replacement. It does nothing special, but it does do everything, just in a way you often would rather it wouldn't. It doesn't have the flexibility of JIRA for the ticketing, and the deploym…

Only alternative outside of GitHub and GitLab I've used was Bitbucket, and it was worse - but this was time when GitHub was good.

There are plenty of open source forges with a better UX.

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

#149
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.

It's not physically possible to run post-mortems for issues at those rates. They should install OpenClaw for that as well.

Perhaps best to simply declare indefinite-mortem

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

#150
New PR: revert GitHub software and infrastructure to version of June 1st, 2018.

New PR: disable new user signups for 6 months

HR initiative: all future KPIs automatically require three-nines availability; all bonuses are forfeited, regardless of accomplishments, if annual availability falls below target

HR initiative: fire CEO and CTO

Post reply on HN