Originally a computational scientist, with skills in high performance computing, I transitioned to software engineering as an independent contractor, specialising in C++.
Why not treat a commit of secrets as like a password leak? Update .gitignore and change the affected password so that the leaked secrets are no longer relevant.
But why not remove it entirely from the repo if we can? It makes commit history cleaner as nothing from .gitignore is available in the previous commits as well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why not treat a commit of secrets as like a password leak? Update .gitignore and change the affected password so that the leaked secrets are no longer relevant.
Yes, We can do it as you've suggested.
But why not remove it entirely from the repo if we can? It makes commit history cleaner as nothing from
.gitignoreis available in the previous commits as well.