GitHub Incident
githubstatus.com
GitHub Incident
1–10 of 99 posts
Re: GitHub Incident
#2I suspect the migration to Azure is continuing to go well
Re: GitHub Incident
#3Microsoft, it's time to hire some SREs.
Re: GitHub Incident
#4I believe it is an Azure outage or some type of MS service - everything on Azure is down.
Re: GitHub Incident
#5Angry unicorns seem to be over.
Re: GitHub Incident
#6I suspect the migration to Azure is continuing to go well
Yes indeed. 6 years of non-stop outages across the platform every month.
Even self-hosting would have been more stable than sitting on GitHub as predicted more than half a decade ago. [0]
Now there is no 'CEO of GitHub' to contact this time (Satya does not care).
Re: GitHub Incident
#7Microsoft, it's time to hire some SREs.
We did hire some, boss! Soshie, Vizzy and Dexter. They're AI, but they're supposed to be way better than a human SRE. At least that's what the Sintra salesguy told us.
Re: GitHub Incident
#8helm repo add gitlab https://charts.gitlab.io/ && helm upgrade --install gitlab gitlab/gitlab
I did this in 2019, it avoided so many headaches. CI is better too since there's a nice clean mapping of build -> pod for everything and I can just exec in if something's borked.
Re: GitHub Incident
#9I suspect the migration to Azure is continuing to go well
I did not come to hacker news expecting comedy gold but you have done it my friend!
Re: GitHub Incident
#10Microsoft, it's time to hire some SREs.
We did hire some, boss! Soshie, Vizzy and Dexter. They're AI, but they're supposed to be way better than a human SRE. At least that's what the Sintra salesguy told us.
So that's what the Tay, and Zoe AI bots were doing all this time after they were cancelled and banned off of Twitter.
Working on the GitHub Azure migration and for years it's gone so well so far.