7 ms·
> And how to really remove a file from your git history.... That's misleading. Once you commit and push it to a remote, you should consider it compromised. You
by craftyguy 8y ago
> And how to really remove a file from your git history....
That's misleading. Once you commit and push it to a remote, you should consider it compromised. You could remove it from the repo and force-push to re-write history, but anyone could have pulled from the same remote since your original push and have the file locally on their system.
A better option is to push a new commit to remove the file from the repo (add to .gitignore), then set a new, strong passphrase/whatever and don't ever use the one you pushed again.
- scarface74 8y agoHow is the article misleading? It said the same thing you did in bold.... Warning: Once you have pushed a commit to GitHub, you should consider any data it contains to be compromised. If you committed a password, change it! If you committed a key, generate a new one.
- craftyguy 8y agoYour comment was misleading, not the article, which is why I quoted you comment and not the article...
- scarface74 8y agoFair Enough....