Git History Rewriting
The cluster discusses the mutability of Git commit history, including methods like force pushes, rebasing, reflogs, and tools for rewriting or cleaning history, along with debates on whether history can be truly deleted or preserved.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Watch out! The "pure and perfect git history is more important than any other consideration" crowd are going to take you apart for this heretical notion!
In git, if you rewrite history, your old history is still available via the reflog; nothing is lost.
Not sure how much good that does. Git history is mutable.
Hello GitJournal author here.I was surprised to read "surprised" cause even if GitJournal choose badly, the history is still there.Nevertheless thanks for letting me know. I'll bump it in my internal Todo list.
thanks. i will have to try it out. but it does sound like "rewriting history" in git et al.
Genuine Curiosity: How else can you destroy/rewrite history in git besides a force push and gc?
Wow that's ugly, particularly the part about hiding the change in the repo history.
Not really erased, maintainers must have a local copy of the history and can just force push
Git allows rewriting history though.
GitHub never deletes anything you push. Even if you rebase and force push, that old information is still accessible. Also why would you drag out such an ugly article to make a point?