Git History Command: The Safer Way to Split, Reword, and Fixup Commits
The git history command is an experimental addition to core Git for the work developers routinely do after the code is already written: split one messy commit, reword an old commit, or fix up a change without reaching immediately for a terrifying interactive rebase.
It is not a replacement for Git. It is a sharper set of scalpels for repairing Git history—and it is worth knowing about before you switch your entire workflow to Jujutsu (jj).
A Hacker News discussion pushed this command onto the front page today, with 372 points and 249 comments when checked. The timing is useful: the feature is new enough to be overlooked, but old enough to have landed across Git 2.54 and 2.55.
What is the git history command?
