3 ms·
I don't think I can agree with that. Accidentally publish secrets/credentials? Rotate them yes but also remove them from the published history. Accidentally p
by torstenvl 4y ago
I don't think I can agree with that.
Accidentally publish secrets/credentials? Rotate them yes but also remove them from the published history.
Accidentally publish a binary for a build tool without the proper license? Definitely remove it (and add it to your .gitignore so it doesn't happen again!)
You discover a major flaw that bricks certain systems or causes data loss? Retroactively replace the Makefile/configure script/whatever to print out a warning instead of building the bad build.
I'm sure there are others.
- GoblinSlayer 4y agoAFAIK, copyright problems are fixed by just another commit without history rewrite. There's also no need to care about outdated credentials. Should bugs be fixed by deleting all history too? That code was buggy, bad, bad, must delete? VCS just becomes glorified ftp this way.