Oh that's why. I didn't connect the dots until I see your message. I had like 5 vscode open and all of them were spamming GitHub PR extension requiring login alert at me.
One thing I hate about GH's status page: sure "auth" gets to live under API, so API gets the downtime report today. But all of my remote git ops are failing, because i was dumb enough to use the `gh` cli to auth. Their status pages are not well defined, but they treat them as such, leading to inflated uptime numbers.
They've been moving it to Azure, presumably partly because they don't want to pay AWS for a thing they could (apparently) do, but more for the appearance of the thing.
I think that's financially sensible in the long run, assuming they believe they can run the thing basically as well on Azure, and aren't expecting major issues during the migration. These have turned out not to be good assumptions.
25 comments
[ 2.7 ms ] story [ 41.6 ms ] threadSomething every week is falling apart at GitHub and it is slowly self-destructing.
Each time there is an incident at GitHub, it is another advertisement to self-host your own. Otherwise just expect GitHub to break next week or two.
Remember, there is no CEO of GitHub; only their AI agents running it into the ground.
[0] https://news.ycombinator.com/item?id=48442572
Like what is the deal here? Why is the company ruining this program? Surely there can't be a financially sensible reason?
I think that's financially sensible in the long run, assuming they believe they can run the thing basically as well on Azure, and aren't expecting major issues during the migration. These have turned out not to be good assumptions.
They should raise their prices!