3 ms·
Mine looks like (on git push): remote: Resolving deltas: 100% (4/4), completed with 4 local objects. remote: fatal error in commit_refs To $REPO ! [re
by openthc 3y ago
Mine looks like (on git push):
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'
Status Page: https://www.githubstatus.com/ https://www.githubstatus.com/ -- actually shows red -- it was almost updated as fast as HN.
- SketchySeaBeast 3y ago> Status Page: https://www.githubstatus.com/ 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.
- paulddraper 3y agoIn a world of green, an accurate status page is a radical act.
- geephroh 3y agoI'd buy this t-shirt
- BossingAround 3y agoIt'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.
- Alupis 3y agoIt's not on accident. There's SLA's and other things on the line when the status page officially recognizes an outage.