Live data from Hacker News

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

githubstatus.com

71–80 of 221 posts

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

#71
post #12

Earlier quoted context omitted.

Name one thing Microsoft didn't run into the ground post-acquisition

I think Minecraft is still in good shape

They deleted my account from 2010 because I didn't convert it to a Microsoft one. They baked an incredibly aggressive chat filter into multiplayer, even if you're not playing on official servers. They've added microtransactions for things that we previously free (skins, resource packs). They force you into their shitty, bloated, user-hostile launcher with adverts.

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

#72
post #12

Earlier quoted context omitted.

Name one thing Microsoft didn't run into the ground post-acquisition

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/

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

#73

Are they running paid marketing campaigns for Gitlab ?

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 deployment machinery doesn't have the fanciness ( and vendor threat ) of chaining github actions, but it does handle both.

I haven't used gitlab, so I'm curious to hear what makes it a "complete mess" too.

* Microsoft's headless chicken naming strategy in full force, it's a miracle they haven't yet renamed and rebranded it to align with copilot yet.

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

#74
post #12

Earlier quoted context omitted.

Name one thing Microsoft didn't run into the ground post-acquisition

hey now, LinkedIn was terrible before Microsoft.

Not as bad as it is now. All I see are suggested posts from people I never connected with and those are full of instagramesque self-promoting banal vibes.

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

#75

Are they running paid marketing campaigns for Gitlab ?

Self-hosting forgejo under tailscale + mirroring public repos through GitHub Has worked wonders for me :)

Ideally those forgejos would safe enough to be on the public internet (and using a federation protocol like activitypub) so we don't have to go through a centralized service such as github and not locked behind private networks (such as tailscale nets)

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

#76

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…

One does not mention TFS in polite company

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

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

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.

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

#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?

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

#79
post #55

Maybe GitHub needs to freeze free repository creation until they get this under control because this is ridiculous.

Or maybe they need to bring back quality assurance expertise to the company.

Yes that would be part of getting things under control, of course.

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

#80

Are they running paid marketing campaigns for Gitlab ?

Self-hosting forgejo under tailscale + mirroring public repos through GitHub Has worked wonders for me :)

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.
Post reply on HN