4 ms·
Git does have a mechanism to remove data from history. It's ugly, and you end up with new commit hashes, but it works. It was designed for situations in which a
by mdavidn 7y ago
Git does have a mechanism to remove data from history. It's ugly, and you end up with new commit hashes, but it works. It was designed for situations in which a developer accidentally adds something sensitive, like a production database snapshot, to source control.
- ptest1 7y agoYeah so you could do a rebase and remove all of the user’s commits, but their work would likely still remain in the subsequent history- integrated as changes in some way. It would be a real mess.
- zbentley 7y agoUsers' contributions (their work) and users' personal information (their metadata) are separate in this case. Cases where they are not separate (think digital signatures/signing keys) are a slightly more complicated question to answer.