2 ms·
> My main concern would be to make sure there are no passwords or secret keys in the data, not how it looks. Worth mentioning specifically: If you make a git (
by stickfigure 5y ago
> My main concern would be to make sure there are no passwords or secret keys in the data, not how it looks.
Worth mentioning specifically: If you make a git (et al) repository public, make sure there are no passwords or secret keys in the history of the repository either. Cleaning a repository history can be tricky, so if this is an issue, best to just publish a snapshot of the latest code (or make 100% sure you've invalidated all the credentials).
- 999900000999 5y agoThe brute force way around this is to remove the .git folder and re init the git repo. For my 2 cents I'd prefer to see sloppy code vs no code. If you did something wrong, you did it wrong. Hopefully someone would put in a PR to fix it
- cephei 5y agoIf there is sensitive data to remove and the history is important to keep, then GitHub has some recommendations for scrubbing the history https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository https://docs.github.com/en/authentication/keeping-your-accou...