Ask HN: Repo encryption and decryption for private repositories on GitHub

Hi all

Considering encrypting repository content before pushing and decrypting after cloning a private repository's content.

Why? The copilot training debacle and disregard for developer's licensing choice. Shows intent, I don't like it.

What's the question? Would it be considered abuse - storage related - if github can not assert what the content is?

Any experiences, professional opinions, and/or tools to enable this without further problems for the organisation in regards to ToS are welcomed.

Thanks, have a great weekend.

construct0

2 comments

[ 2.6 ms ] story [ 29.1 ms ] thread

Would an encrypted repo not completely obfuscate history?

Good take - didn't think about it in that context - encryption could happen on a per-file basis perhaps?

That would allow for enough clarity together with a well-written commit message and description, in my opinion.