Executive TL;DR:
- The Git history command is a powerful tool for managing commits.
- It allows for rewriting and editing of commit history.
- Some developers are skeptical about using this command.
The Buzz Score
The Internet’s Verdict: 70% Hyped, 30% Skeptical
Forum Voices
Developers have mixed opinions about the Git history command. Some find it useful, while others are cautious.
> scary rebase -i commands that can leave your tree in a half-broken state if you so much as sneeze `git rebase –abort` exists. One can also set a tag or something before doing the rebase, do whatever, then `git reset –hard $set_tag` to go back. Nothing to be scared of. Not like the prior state is lost.
Others are concerned about the potential risks of altering commit history.
Granted, I have a perspective of a game dev, but this kind of repo defiling just gives me the willies. IMO instead of finding a common ancestor and altering it, just make the desired change upstream and merge it to where it’s needed.
Conclusion
The Git history command is a powerful tool that can be useful for managing commits, but it requires caution and careful consideration.
Focus Keyword: Git History
