3 ms·
It "works offline" in that you can create commits, view project history, and view every branch while offline. But fetching and pushing are such a common part of
by profmonocle 4y ago
It "works offline" in that you can create commits, view project history, and view every branch while offline. But fetching and pushing are such a common part of an engineer's day-to-day workflow that a poorly-timed outage of your remote repo is very disruptive, especially if you use git for deployment.
- astrange 4y agoYou can fall back to the actual intended git development model, emailing each other patches with `git format-patch` and `git am`. Not that code reviews of diffs over email are all that great.
- acdha 4y agoThis is technically true but the number of GitHub outages which have prevented you from doing that for more than a couple of minutes is pretty low. In comparisons like this, the more important question is not “is GitHub perfect?” but rather “what are you comparing it to?” — internal systems are notorious time-sinks and productivity levels from using GitHub normally are high enough that I think it'd be quite fair to conclude that you're still well ahead of where you'd be even if you have an extended coffee break once or twice a year.
- qudat 4y agoNot to mention if you rely on gh actions for ci/cd. I think it makes sense for them to migrate to git and github, but I've been slowly migrating most of my code to sr.ht or self-hosted mirrors. Email patches work pretty well for smaller teams.
- encryptluks2 4y agoGit is literally an SSH sever so management is not a complex as you think.
- baq 4y agoit's disruptive the first time you have to do it without github; afterwards it should be only a few tweaks in your git repo url configs