Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub was having issues

githubstatus.com

Post reply on HN
Print view View original

91–100 of 231 posts

Re: GitHub was having issues

#91

Post by cddotdotslash »

everfrustrated wrote: post #42

Enterprise customers, remember to email your sales rep and ask for them to report on their contracted uptime with you that you are allowed to do as per contract. They wont do this unless you ask hoping you don't notice the outages. It creates lots of internal pain - they have no automation internally for reporting on this. This is the only way anything will ever change. GitHub is _easily_ the most unreliable SaaS pro…

Companies should automate this. Write their own outage monitoring, feed the results, plus the cumbersome format you have to send to the provider, into an LLM, have it spit out an email requesting SLA credits or whatever the contract specifies.

Probably not worth it for low cost services, but if you’re paying GitHub $x millions per year, maybe it is.

Re: GitHub was having issues

#92

Post by jeltz »

makkesk8 wrote: post #73
jeltz wrote: post #59

Earlier quoted context omitted.

Any important feature from Gitlab you feel is missing? I personally think Gitlab has way more features than I need but maybe there are some important ones I would miss.

Running Gitlab in any kind of scale beyond a single server is a major PITA. And it's very poorly optimized.

That I am well aware of. I hate running Gitlab. I jsut wonder what different features different people are missing.

Re: GitHub was having issues

#93

Post by dymk »

taude wrote: post #68

git was designed as a distributed vcs for high-latency connected developers with plenty of ability to work offline. I don't think I've really been impacted by any of the outages. Maybe I wait an extra hour to merge a feature or something, in which case I actually get to eat lunch and browse HN, doesn't feel quite as catastrophic for me, as some of you.

GitHub is everything in addition to the git hosting. Issue tracking, code review, CI, artifact hosting, wiki+docs, kanban board.

Re: GitHub was having issues

#94

Post by koiueo »

taude wrote: post #68

git was designed as a distributed vcs for high-latency connected developers with plenty of ability to work offline. I don't think I've really been impacted by any of the outages. Maybe I wait an extra hour to merge a feature or something, in which case I actually get to eat lunch and browse HN, doesn't feel quite as catastrophic for me, as some of you.

GitHub isn't just git, it's also a CI, a project management tool/issues tracker...

Re: GitHub was having issues

#95

Post by metalliqaz »

meepmorp wrote: post #45
metalliqaz wrote: post #25

Dear sages of HN, what is the scrappy new upstart project that will rise up to take Github's place? Because this is becoming intolerable.

It's kind of weird that we've collectively decided on a distributed version control system, while centralizing where we keep the repositories and metadata.

I think it's just a simple reality that most projects don't actually need or want a decentralized development process. In my experience, most projects are looking for a single, high-reliability canonical source that is in control of project leadership. Most projects are only developed by a small group, maybe even only one person.

Re: GitHub was having issues

#97

Post by jeltz »

homebrewer wrote: post #77
dzogchen wrote: post #56

Earlier quoted context omitted.

Much simpler. Much less features. Completely open source and not only the core.

Depends on your needs. Last time I checked, Gitlab wanted money for e.g. assigning multiple PR reviewers, which is available in gitea/forgejo. The real issue with gitea/forgejo compared to Gitlab is their terrible CI, which is (to some approximation) a clone of GitHub Actions, also a dumpster fire for those of us proficient with/preferring the UNIX command line. You'll probably need a separate CI runner, like Woodpec…

Gitlab CI is so much better than Github Actions. With some additional improvements Gitlab CI could become amazing.

Re: GitHub was having issues

#100

Post by sashank_1509 »

chaz6 wrote: post #80
sashank_1509 wrote: post #76

I’m at Google, we have a million + file codebase. Every piece of code is snapshotted (no need to commit, automatic snapshot whenever a change is made). Every line of code has its own unique URL (this is for your branch too, not just overall). Background tests running nonstop hourly. Never seen any downtime. The infra at Google is insane

Without manual commits, is there any way to record the intention of each change?

Yes you can still commit as a logical delineation of changes. And every commit is automatically a PR, folding multiple commits is possible but not the common workflow, they prefer just reviewing and approving each commit.
Post reply on HN