5 ms·
Good point -- frankly I'd suggest doing both (clean repo and revoke/replace the secrets). The developer in question simply overlooked the issue, and since we we
by moot 12y ago
Good point -- frankly I'd suggest doing both (clean repo and revoke/replace the secrets). The developer in question simply overlooked the issue, and since we were busy spinning down the company, nobody else caught it.
- stouset 12y agoAlso, just swear of ever committing secrets to a repo to begin with. It's a bad idea, period.
- StavrosK 12y agoThere are many times when that isn't doable. Fortunately, you can swear off ever committing plaintext secrets to a repo. I use git-crypt: https://github.com/AGWA/git-crypt https://github.com/AGWA/git-crypt