remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
remote: fatal error in commit_refs
To $REPO
! [remote rejected] main -> main (failure)
error: failed to push some refs to '$REPO'
I think we should applaud this when it actually happens. Far too many services are terrible for this. While I'd rather the service not be down, it makes me feel a bit better if they don't lie about it.
It's funny when a company like Amazon, which many would think is on the cutting edge of automation, implements their status page as a manually updated static page.
Comments
Mine looks like (on git push):
Status Page: https://www.githubstatus.com/ -- actually shows red -- it was almost updated as fast as HN.I think we should applaud this when it actually happens. Far too many services are terrible for this. While I'd rather the service not be down, it makes me feel a bit better if they don't lie about it.
In a world of green, an accurate status page is a radical act.
I'd buy this t-shirt
It's funny when a company like Amazon, which many would think is on the cutting edge of automation, implements their status page as a manually updated static page.
It's not on accident. There's SLA's and other things on the line when the status page officially recognizes an outage.