3 ms·
I wonder whether something like [0] would work, where the repository is encrypted on push and decrypted on pull. Might be against Github's terms of use, though.
by caipre 12y ago
I wonder whether something like [0] would work, where the repository is encrypted on push and decrypted on pull. Might be against Github's terms of use, though.
[0]: https://rovaughn.github.io/2015-2-9.html https://rovaughn.github.io/2015-2-9.html
- MollyR 12y agothat's a really cool idea.
- duaneb 12y agoWhy would that be against github TOS? Encrypted files in git are not exactly unusual.
- caipre 12y agoMy thinking was that it's effectively a private repository (albeit publicly visible), so it would subvert their business model.
- soperj 12y agothey were talking about it being a private repo anyway that they were worried about.
- duaneb 12y agoWell, it'd be pretty shitty. Diffs would be binary and practically useless; merges would have to be entirely manual. Github would lose more in brand trust than they would gain in saved costs on those repos (or lost revenue).
- emmelaich 12y agoOr perhaps https://github.com/AGWA/git-crypt