61–70 of 90 posts
Do Github publish post-mortems? Incidents spiked recently and I wonder what's repeatedly causing the issue. Mistakes (preventable or not) can happen, but repeated failures is a systematic issue.
It's the second day in a row now where the main HN post about GitHub downtime has had "GitHub" edited out of the post title.
I'm frustrated with GitHub's stability, too, but we should be clear that GitHub wasn't down. They're one of the more honest services when it comes to posting service degradations, unlike some other platforms where teams will resist updating the status page until it's an undeniable site-wide outage. > We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Ho…
Earlier quoted context omitted.
> Why are you still using Github? Stars. Grifters have discovered vibe-coding and the ability to buy GitHub stars, followers, etc. https://duckduckgo.com/?q=buy+GitHub+stars&ia=web
Why do stars and followers matter? Who is looking at them?
I'm frustrated with GitHub's stability, too, but we should be clear that GitHub wasn't down. They're one of the more honest services when it comes to posting service degradations, unlike some other platforms where teams will resist updating the status page until it's an undeniable site-wide outage. > We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Ho…
They're being forced to be less dishonest. They're not going to count this as downtime anyways. They're reporting 100% uptime for April: https://www.githubstatus.com/
Why don’t they just raise GitHub actions prices? Supply and demand, that would sort itself
Another challenge is that the GitHub Actions paid tier is already very expensive, the quality of service is poor, and they have major security challenges. They could load shed by raising prices, driving customers to other platforms, but they already charge 10x what others charge (https://runs-on.com/pricing/#runner-pricing, https://www.ubicloud.com/docs/about/pricing). Anyone using GitHub Actions at scale would be somewhat price insensitive already.
Do Github publish post-mortems? Incidents spiked recently and I wonder what's repeatedly causing the issue. Mistakes (preventable or not) can happen, but repeated failures is a systematic issue.
It also seems like the HN mods want to downplay the GitHub outages. It's the second day in a row now where the main HN post about GitHub downtime has had "GitHub" edited out of the post title.
Earlier quoted context omitted.
- There are already viable GitHub replacements, like Codeberg, Bitbucket, Gitlab, etc. Everyone stays on Github for network effects, not because of the superior product. You can't vibe code network effects. - And yes, GitHub is a massive product with like 50 different huge features. No reasonable person would say you can trivially vibecode that. Vibecoding would still make it easier. I feel this argument is a bit sil…
Why do network effects matter for "in-house" (i.e. corporate/commercial) software work? Open-source projects, yes I can sort of get it, you want to be where the contributors are (but there are downsides to that also).
How is the company morale at github? I imagine it to be really very depressing working at github right now with all these downtime. I know github is being used by AI agents like there is no tomorrow but there have also been en-shittification attempts at github and I have seen some comments tell me that github can be more efficient. So what are people who are at github doing right now? Like what do the priorities look…
Since we're guessing I could also imagine the opposite: stressful sure and heaps of work, but numbers absolutely through the roof, and lots of opportunities, bonus/promo-boosting wins, etc.
Earlier quoted context omitted.
It also seems like the HN mods want to downplay the GitHub outages. It's the second day in a row now where the main HN post about GitHub downtime has had "GitHub" edited out of the post title.
That's standard for HN and explicit in the guidelines linked in the footer. No need to include the company/domain in the title, and it should match that on the submitted page. Which is 'Incident with Actions' as it reads here (now) too.
It's not like OP is running out of space in the HN title, either. How is "Incident with Actions" more user-friendly than including "GitHub outage" in the headline?
Furthermore, the subtitle of the OP is "Incident Report for GitHub," so why not just include this if we need to follow the rule so carefully?
Earlier quoted context omitted.
Why do network effects matter for "in-house" (i.e. corporate/commercial) software work? Open-source projects, yes I can sort of get it, you want to be where the contributors are (but there are downsides to that also).
A ton of third-party tools only work with the most popular providers, github, and then gitlab, then nothing, then the rest.