&gt; I disagree, cloud backups are more reliable.<p>You&#x27;re taking this out of context. It does not download this data from Github, <i>and then remove the data from Github</i>. So the data is still &quot;backed up&quot; in the cloud, but is also now backed up locally. How is this not more reliable?<p>This also does not preclude the ability to push your backup to <i>another</i> cloud provider (e.g. S3, Dropbox, etc) to distribute your backups across the cloud.<p>&gt; If the repo goes down it&#x27;s already going to be a lot harder to use, but it seems easier to fork a repo.<p>A fork does not maintain things like comments and issues on the original repo, which github-backup does backup.<p>&gt; When have you not been able to work on a local repo locally?<p>Github does not stick things like Github Comments or Github Issues directly into your repository. If you are (e.g.) relying on Github Issues to track things to do on your repo, then you&#x27;re out of luck on a plane without access to that.<p>&gt; Overall, I think I&#x27;m missing the point.<p>It seems like you&#x27;ve ignored the list of things that github-backup actually does, and commented on it from that point of view. He lists the things that github-backup does, but you have commented on none of them. For example, why did I have to explain to you that it backs up Github Comments and Github Issues on your repository? Were you under the impression that these things were already in your repo? Do you use Github without these things to the point were you didn&#x27;t know that they existed, or can&#x27;t see the use-case where someone would use them? I&#x27;m a little confused.