Just completed one or our (quarterly) github exports before this hit... If people are looking into extracting everything from their organisations, i've published the scripts I use: https://github.com/sigio/github-export
GitHub was having issues
101–110 of 231 posts
Re: GitHub was having issues
#102Enterprise 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…
> GitHub is _easily_ the most unreliable SaaS product. Some of us are stuck using Atlassian and BitBucket and it is by far worse in every way.
Amen, BitBucket outages are regular and showstopping. Self hosting is genuinely more reliable.
Re: GitHub was having issues
#103git 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.
That makes sense, I wasn't sure how "all in" everyone is on these other features that are only github centric.
Re: GitHub was having issues
#104Enterprise 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…
> GitHub is _easily_ the most unreliable SaaS product. Some of us are stuck using Atlassian and BitBucket and it is by far worse in every way.
It's also _by_far_ the cheapest, and most git-work can be done offline, so while it's inconvenient, it's not stopping all operations here.
Re: GitHub was having issues
#105Any one else smile for a moment when they saw their issues list empty? Don't rush to fix it ;)
Re: GitHub was having issues
#106I've always used Bitbucket as it allows private repositories, so Github was never something I wanted to use. But it is one of the most important websites in the world for tech people and should be run better than this, especially being now owned by the largest tech company in the world. On the other hand, it just shows that centralisation, or over-reliance on one thing or service, is always the worst idea. But people…
Github switched from unlimited users and per-repo fees to unlimited private repositories and paying per-seat 10 years ago or so: https://github.blog/news-insights/product-news/introducing-u...
Re: GitHub was having issues
#107Maybe they should focus less on "agentic" and more on just keeping their core product solid... I suppose that doesn't rhyme with growth at all cost... zzz sad... it is
Re: GitHub was having issues
#108Too many unnecessary features at this point perhaps. Self hosting might be a good alternative. Don't need the UI.
Re: GitHub was having issues
#109I’m really wondering what internally causes this. No one likes it when they have outages, but it keeps happening. Is this a culture thing? Like pressure to ship features fast? Some under staffed teams or lack of ownership on some crucial components?
Re: GitHub was having issues
#110Earlier quoted context omitted.
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.
Yeah, I think what people really liked about git (vs many other VCSs at the time) was cheap and easy local branching, not the distributed nature.