I suspect the migration to Azure is continuing to go well
This feels more like Copilot-as-platform-engineer to me
Github's been running on vibe code for a while now and it's starting to show
GitHub Incident
71–80 of 99 posts
Re: GitHub Incident
#72Perhaps the gemini-cli bot arguing with itself is taking its toll https://github.com/google-gemini/gemini-cli/issues/16750
https://github.com/google-gemini/gemini-cli/issues/16723 is even worse, GitHub shows `5195 remaining items` in the collapsed timeline.
Wow. If you look at all the issues this seems pretty common
https://github.com/google-gemini/gemini-cli/issues?q=is%3Ais...
Re: GitHub Incident
#73Github's recent reliability has honestly been abysmal. Not surprised.
Unless some major customers are moving away, I don't think they are going to seriously care about it.
What is the quality-first, high uptime alternative to GitHub? My employer uses both GitHub and GitLab, and while I think GitLab is better, its quality also frankly sucks. It's riddled with bugs that have just been marinating on the issue tracker for years, and the most common "fix" for gnarly bugs in the CI platform is "revise the documentation to reflect the existing (broken) behavior".
Re: GitHub Incident
#74Days since last GitHub incident: 0.2
Re: GitHub Incident
#75Days since last GitHub incident: 0.2
14 incidents this month. So far.
Re: GitHub Incident
#76Good thing git is a distributed system
True, workers can still commit to their local git. I've been looking into having a separate git server that we can commit to and add plain ole git hooks to, and just having it be synced with github as a clone.
Check out Gitea. Its kind of a clone of github but you can self host.
Re: GitHub Incident
#77Earlier quoted context omitted.
Unless some major customers are moving away, I don't think they are going to seriously care about it.
What is the quality-first, high uptime alternative to GitHub? My employer uses both GitHub and GitLab, and while I think GitLab is better, its quality also frankly sucks. It's riddled with bugs that have just been marinating on the issue tracker for years, and the most common "fix" for gnarly bugs in the CI platform is "revise the documentation to reflect the existing (broken) behavior".
It's amazing, before we even had ChatGPT, GitLab was building so much endless slop halfbaked crap in their pursuit of ever more "enterprise checkboxes". Now they have slowed right down, no doubt collapsing under the escalating maintenance weight of all the nonsense that was created, like the canaries in the vibe coding mines telling us of impending doom.
Now you go to their blog, theres a banner at the top announcing "GitLab Agentic AI whatever is GA (GENERAL AVAILABILITY)" and you try to click it its literally a fucking 404 not found. That's the level of their stability and quality. Try it for yourself:
Re: GitHub Incident
#78Earlier quoted context omitted.
Having just had to buy 4TB of RAM, I appreciate this.
That's like 100,000 USD. I keep thinking about making a rap video wearing a 10 TB gold chain surrounded by big booty girls with their naughty bits covered in m.2 SSD's while dissing the AI industry. Though I cant afford the RAM :-/
Use Veo