Because this needs to happen as one prepares to push to day's last deploy. Back to backups. Have backups for critical systems, people. In my case, it's building docker containers locally and luckily deploying to one server via ssh.
Because if you don't spend multiple days per year managing your own "backup" to GitHub, you might be left unable to push to GitHub for a few hours per year? btw, I hope none of your CI system relies on build steps that might include pulling code from GitHub or downloading packages from GitHub Package registry. Often when GitHub is down, my CI system on GitLab is broken too.
GitHub issue - resolved
81–90 of 169 posts
Re: GitHub issue - resolved
#82HN should really have a “Down HN” category, as this is the most reliable place to get this information.
Everytime something has degraded performance or is down for me: 1. check my internet connection 2. check HN 3. check official statuspage
1. the status page is unavailable too
2. the status page reports the service as green/available even though it's red/down (maybe it's still accessible to the service pinging its health status, maybe it's "accessible" but not actually functional, maybe the engineers were too busy fixing the problem to click the button to update the status page, maybe not updating the status lets them pretend they're within SLAs or KPIs)
Re: GitHub issue - resolved
#83HN should really have a “Down HN” category, as this is the most reliable place to get this information.
Re: GitHub issue - resolved
#84Earlier quoted context omitted.
Because if you don't spend multiple days per year managing your own "backup" to GitHub, you might be left unable to push to GitHub for a few hours per year? btw, I hope none of your CI system relies on build steps that might include pulling code from GitHub or downloading packages from GitHub Package registry. Often when GitHub is down, my CI system on GitLab is broken too.
Is there anywhere a history of the uptime of GitHub?
I suspect what you're getting at is that the downtime might evaluate to multiple days over the course of the year. Maybe that's true, idk. I'd be curious, but you'd probably want to do the analysis separately for different services (e.g. Actions vs. Package Registry vs. Git outages all have different effects on build infrastructure downtime).
Re: GitHub issue - resolved
#85Re: GitHub issue - resolved
#86I used to get my github status updates in slack via an RSS feed, and just searched for the feed again, but its gone? Is there an alternative for this?
Re: GitHub issue - resolved
#87Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.
Re: GitHub issue - resolved
#88HN should really have a “Down HN” category, as this is the most reliable place to get this information.
Everytime something has degraded performance or is down for me: 1. check my internet connection 2. check HN 3. check official statuspage
Re: GitHub issue - resolved
#89Suppose you start your day by downloading some code from GitHub to work on. This morning you would be stuck. Do you save code on your hard drive or company servers or GitLab to handle this risk?