Is GitHub deployed using GitHub Actions?
I was talking with some GH sales/marketing engineers last month and they said it deploys with actions, but they have a custom deploy queue
Days since last GitHub incident
71–80 of 142 posts
Re: Days since last GitHub incident
#72I've been getting some weird cryptocurrency spam notifications on GitHub and they can't be cleared for some reason. Blue dot is gonna be there forever apparently. Some users made an issue out of it but nobody cared to fix it.
Same happened to me. You can clear it via the CLI, hilariously. ``` gh api notifications\?all=true | jq -r 'map(select(.unread) | .id)[]' | xargs -L1 sh -c 'gh api -X PATCH notifications/threads/$0' ```
HN doesn't support markdown, but you can "code" format it with 2+ spaces.
Re: Days since last GitHub incident
#73I guess none of us really needs those 9s, and even two 9s are just good enough. I even doubt whether *SOME* of the banking transactions really really really need those 9s too -- like, I don't really mind if 1 out of 100 credit payment doesn't go through so I have to do it again -- it does happen once for a while and I just swiped it again.
GitHub has a container registry. That going down can cause pod start failure. I agree the source code probably doesn't need infinite nines, but the container registry is different.
Which should not even be that hard, because read-only replicas of artifact repos are trivial to create and easy to loadbalance.
Re: Days since last GitHub incident
#74I've been getting some weird cryptocurrency spam notifications on GitHub and they can't be cleared for some reason. Blue dot is gonna be there forever apparently. Some users made an issue out of it but nobody cared to fix it.
This should have been fixed here: https://github.blog/changelog/2025-12-04-notifications-trigg...
Are you still seeing it, would you mind checking? Our team will get on it if so.
Re: Days since last GitHub incident
#75At this point, is there any downside to switching to GitLab?
Is the uptime any better?
Not really:
GitHub - Historically, GitHub reports uptime around 99.95% or higher, which translates to roughly 20–25 minutes of downtime per month. They have a large infrastructure and redundancy, so outages are rare but can happen during major incidents.
GitLab - GitLab also targets 99.95% uptime for its SaaS offering (GitLab.com). However, GitLab has had slightly more frequent service disruptions compared to GitHub in the past, especially during scaling events or major upgrades. For self-hosted GitLab instances, uptime depends heavily on your own infrastructure.
Re: Days since last GitHub incident
#76Re: Days since last GitHub incident
#77At this point, is there any downside to switching to GitLab?
Is it any better ?
We had that last year, with the full premium stuff ("pay as much as we can" mindset)
Please see this: a basic feature, much needed by lots of people (those who are stuck on azure ..): https://gitlab.com/gitlab-org/gitlab/-/issues/360592
Please read the entire thread with a particular attention to the timeline
Re: Days since last GitHub incident
#78[flagged]
It's just a metric, not "whining". Besides, if complaining about companies (whether it's Github/Microsoft, Anthropic, Google, etc) without offering a solution is out-of-bounds, that probably knocks out 50% of the posts and comments on HN.
Re: Days since last GitHub incident
#79At this point, is there any downside to switching to GitLab?
What’s gitlab? (Snarky way of saying: GitHub still has huge mindshare and networking effects, dealing with another forge is probably too much friction for a lot of projects) Not that GitHub doesn’t suck…
When GitHub was bought by Microsoft, Gitlab made moving your repos to them super easy. Apparently not enough people have moved and it would seem even with sustained attacks from all kinds of different vectors, it would seem people continue to stick with them.
I use both Gitlab and Github and have yet to experience any downtime on any of my stuff. I do however, work at a large corporation and the latest NPM bug that hit Github caused enough of a stir where it basically shut down development in all of our lower environments for about two weeks so there's that.
But I do agree, and it seems like their market share increased after the Microsoft acquisition which is contrary to what I heard in all my dev circles because of how uncool MSFT is to many of my friends.
Re: Days since last GitHub incident
#80I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…
None of the open weights models you can run locally will perform at the same level as the hosted frontier models. Some of them are becoming better, but the step-down in output quality is very noticeable for me. > If Github sold a $5000 box I could plug into a corner in my house and just use that entire experience locally I'd seriously consider it. I'm guessing maybe I could get partway there by spending twice that on…
Thank you, a bit sad to hear that local inference isn't really at this level of performance yet. I was previously using the VSCode agent chat and playing with both OpenAI and Github hosted models but I switched to using the Github web UI directly a lot since my workflow became a lot more issue/PR-focused. Sounds like I should probably tighten up the more generic IDE-centric workflow and make it a keyboard shortcut to switch around when a given provider is down. I haven't actually used Claude directly yet but I think Github agents often use it under the hood anyway.