Incident with Github.com [resolved]
71–80 of 1001 posts
Re: Incident with Github.com [resolved]
#72Re: Incident with Github.com [resolved]
#73Re: Incident with Github.com [resolved]
#74Re: Incident with Github.com [resolved]
#75Re: Incident with Github.com [resolved]
#76Can anyone shed some light why GitHub is having so many problems lately?
Copy/paste of a comment I posted a couple months ago: I am not trying to make any excuses for GitHub, however I recall one tweet that made my eyes bug-out: > Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) > GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week i…
Re: Incident with Github.com [resolved]
#77Re: Incident with Github.com [resolved]
#78We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?" No idea if/when we decide to pull that bandaid but I think once we can't merge a hot fix into main because of GH being down, it'll be a big org push to replace it. What's everyone else using? Self hosted Gitlab? Gitea?
Re: Incident with Github.com [resolved]
#79[flagged]
Re: Incident with Github.com [resolved]
#80I had a lot of goodwill for GitHub but I think today is the tipping point. Looking at a unicorn page, I feel this lingering hope that it's transient (like it usually was in the old days) but my mind reassures me it's probably going to be a long full outage again. The hope is dead.
I guess they're quite happy with that TBF, it doesn't seem like they're that interested in being a git forge anyway.