GitHub falls offline, devs worldwide declare today a snow day Popular and widely used source-code hosting service GitHub is, for the moment, no longer a widely used source-code hosting service. It has fallen offline. Since 1632 PT (0032 UTC, 1132 AEDT), the website has been down. Right now, the San Francisco-headquartered upstart reports: "We're investigating a significant network …
Exactly, so unless you were trying to push to the central/public repo it shouldn't stop you at all.
All this did for me was just that - push it to the public repo. It wasn't until about 3am UK time (insomnia before any one asks) before I was able to do that.
"That pretty much locks out a big wedge of open-source project developers from their Git-controlled source code"
a) It does seem quite online for me right now and b) we all do know that every cloned git repo is a complete local copy of all the files involved, on which you're welcome to code / compile / commit as long as you don't need to actually share your changes, right?
Github goes offline and developers suddenly discover what 'git remote add' does. Well they asked a mate who knows git ;)
git is a distributed source control system and things like github, though helpful really aren't needed for work to continue (who uses an issue list that isn't yellow notes on the wall). I suspect more repos pushing backups to bitbucket.org aka git remote add backup git@bitbucket.org : mycompany/crown-jewels.git
My main issue with git in general is remembering to push my commits and that's on my personal repos on my NAS.
So I suspect many people barely noticed and perhaps (like me) just expected their cron jobs to push their branches when they were available.
Merges would have been much more problematic.
With git, virtually everything that you do on it is completely offline and distributed, so most of what people do in git on a day to day basis isn't actually affected by whether github is online or not. Github is basically just a convenient place to store a definitive copy of the repository, and provides nice dev tools like pull requests. But as far as creating branches, writing code, and committing it goes - you do that totally independently of github. My point here is just that working locally is the normal state of affairs in git, rather than something that you would do in some kind of emergency situation.
Speaking from my experience, the sorts of things that are more likely to be affected by this are things like automated builds, deploying changes and code reviews (via github pull requests). But these issues aren't anything specific to git or github, since you'd have the same issue if any centralized repository went down, and you could easily sort it in an emergency by updating your build server or other tools to point at a copy of the repository (which every dev has on their machines by virtue of the way git works).
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
