Hacker News Reader

Comment by odo1242 | Hacker News Reader

To be fair to GitHub, outages are pretty short (~40 minutes), and they rarely impact critical parts of the service, nor do they affect one’s ability to work (git offline)

View on HN

What... what parts of GitHub would you consider "critical parts of the service" if not git operations, pull requests and CI?

Production has a critical error and we need to push a fix while our whole build pipeline runs on GH CI. Which is not working. Thank God their critical parts never break.

Not being able to push is pretty critical.

git push ending up with Internal Server error is similar to save file ending up with disk full error. yes, it can work after 40 minutes, and one can go to lunch and retry later, but here in Europe the troubles started at the end of a (normal) workday.

I'm not able to get code pushed, meaning I can't address PR feedback, meaning I can't get things approved, meaning code isn't getting merged to main and thus a ticket isn't getting closed. Sounds pretty critical to me.

If I can't push my code, I'd say that's a critical issue. And if my Actions won't run (that I pay for), I'd also put that in the critical issue bucket.

I'm going to be investigating self hosting, this is ridicolous.

40 minutes is an eternity when you can't push to a gitops repo with a PRD issue.

... and that is (yet another example) why pipeline driven gitops is a really darn bad idea.

If I had a super critical gitops pipeline that couldn't deal with the odd provider outage I'd be using my cloud providers repo service.

Same as with container registries; prod shouldn't be pulling from Dockerhub.

In Mars, right?

Good bait

Reply on news.ycombinator.com