Hacker News Reader

Secrets in code is bad practice because it puts the secrets in source control and gives them to anyone with access to the code.

You separate out the secrets to keep them secret.

Next evolution of Git should automatically introspect the code base for comment to leaving out all "secrets".

My point is, make the code easy to clone in a runnable shape wihtout any hacking on host system.

You can configure GitLab to reject the push if you comitted secrets, based on regex marching with common formats for tokens.

What company do you work for? I'd like to cancel my subscription.

Seriously...bad idea. One repo leak or even one bad copy/paste in StackOverflow and you're done.

It's not a problem. Here you go: https://github.com/AGWA/git-crypt

This only works if secrets are frequently rotated and contain enough entropy. Else, all secrets will eventually be decrypted from leaked repositories and distribution artifacts.

Hell yeah brother. Move fast and break things philosophy