Git 2.54 Release Overview
The open-source Git project has rolled out version 2.54, bringing a host of enhancements and bug fixes contributed by over 137 developers, including 66 first-time contributors. This release builds upon the foundation laid by Git 2.52, and this article highlights the most notable features introduced in both Git 2.53 and 2.54.
The New git history Command
One of the standout additions in Git 2.54 is the experimental git history command, designed to simplify common history rewriting tasks. While Git has long offered powerful tools like git rebase -i for reordering, squashing, editing, and dropping commits, that flexibility often comes with complexity. For straightforward operations—such as fixing a typo in a commit message three commits back or splitting a commit into two—the full interactive rebase workflow can feel excessive, requiring you to create a to-do list, mark commits for editing, and manually drive the rebase to completion.
The git history command addresses these simpler cases with two initial operations: reword and split. Both avoid touching your working tree or index, making them lightweight and efficient.
Reword: Edit Commit Messages Without Interruption
With git history reword <commit>, you can open your editor directly on the specified commit’s message. After editing and saving, Git rewrites the commit message in place and updates any branches that descend from that commit. Unlike an interactive rebase, this operation does not alter your working tree or index, and it even works in bare repositories. This makes it ideal for quick fixes to commit messages without the overhead of a full rebase.
Split: Divide a Commit Into Two
The git history split <commit> command lets you interactively split an existing commit into two. You select which hunks (individual changes) should be carved out into a new parent commit, using a familiar interface similar to git add -p (interactive staging). For example:
$ git history split HEAD
diff --git a/bar b/bar
new file mode 100644
index 0000000..50810a5
--- /dev/null
+++ b/bar
@@ -0,0 +1 @@
+bar
(1/1) Stage addition [y,n,q,a,d,p,?]? yAfter you select which hunks to include, Git creates a new commit with those changes, makes it the parent of the original commit (which retains the remaining hunks), and rewrites any descendant branches to point at the updated history. The result is a clean, targeted split without altering anything else.
Limitations and Design Intent
By design, git history is meant for targeted, non-interactive rewrites, not open-ended history rewriting. It intentionally does not support histories containing merge commits, and it will refuse any operation that could result in a merge conflict. This keeps the command simple and safe for its intended use cases, while the powerful git rebase -i remains the go-to tool for complex rewrites.
Under the Hood: Built on git replay
The git history command is built on top of the core machinery of git replay, which was extracted into a library as part of this work. This modular approach not only makes git history possible but also paves the way for future tools that can leverage the same robust replay engine.
Other Notable Improvements in Git 2.53 and 2.54
While the git history command is the headline feature, Git 2.54 (along with 2.53) includes numerous other enhancements, performance improvements, and bug fixes contributed by the community. These include updates to git bisect, better handling of sparse checkouts, and refinements to the git log output. For a complete list, refer to the official Git release notes.
Conclusion
Git 2.54 delivers a thoughtful addition with the experimental git history command, making common history rewriting tasks faster and less error-prone. By focusing on targeted operations like reword and split, and building on a solid replay engine, Git continues to evolve to meet developers’ needs. Whether you’re fixing a commit message or splitting a change, git history offers a simpler alternative to the full interactive rebase workflow.