git history ist neu (und experimentell) in Git. Damit versuchen sie, die üblichen Operationen zum Neuschreiben der History, die sonst immer gefummel sind, einfacher zu machen:
usage: git history fixup <commit> [--dry-run] [--update-refs=(branches|head)] [--reedit-message] [--empty=(drop|keep|abort)]
or: git history reword <commit> [--dry-run] [--update-refs=(branches|head)]
or: git history split <commit> [--dry-run] [--update-refs=(branches|head)] [--] [<pathspec>...]In der nächsten Version 2.56 kommt auch noch dazu:
git history drop <commit-id>This command will cause the identified commit to be removed from the history of the current branch, replaying all commits that were added after it. It offers an easier way of removing an offending commit. Unfortunately, it still refuses to work if the history contains merge commits, making it unusable for many (or most) repositories.