The open-source Git project released Git 2.55 on June 29, 2026, with features and bug fixes from over 100 contributors, 33 of them new to the project , delivering a set of workflow improvements that developers who use the command line every day will notice immediately.
Parallel hooks cut wait times in multi-step pipelines
Git 2.54 introduced hooks defined through configuration files rather than only as executable files in $GIT_DIR/hooks, making those hooks easier to share, compose, and selectively disable without copying scripts into each repository’s hooks directory. Git 2.55 extends that work by allowing compatible configured hooks to run in parallel.
For example, a project might have independent pre-commit hooks for linting and unit tests; if both declare hook.<name>.parallel = true, Git can run them at the same time. The number of concurrent jobs can be controlled globally with hook.jobs, per event with hook.<event>.jobs, or on the command line with git hook run -j.
The change matters most on larger repositories where pre-commit checks have multiplied over time. All hooks ran sequentially up to Git 2.54 inclusive, regardless of where they were defined.
Parallel execution means the total wall-clock time shrinks to the slowest single check rather than the sum of all of them.
The git history command keeps growing
The headline feature of the preceding Git 2.54 release was the experimental git history command. In Git 2.54, that command supported reword and split, giving users a narrower tool for editing commit history than the more flexible but more complex interactive rebase workflow.
Git 2.55 extends that with git history fixup, alongside a safer git checkout -m, fsmonitor support on Linux, and remote-group push.
git rebase -i, though powerful, can be unnecessarily complex for minor edits: an interactive rebase operates on a range of commits, updates the working tree and index as it goes, and can leave the user in a conflicted state that must be resolved before proceeding. git history reword updates commit messages directly, while git history split lets users split commits without a full interactive rebase.
The command does not modify the working tree or index, meaning it can also operate on bare repositories.
The addition of fixup in 2.55 extends that philosophy further, letting a developer fold small corrections into an earlier commit without launching the full rebase to-do list. GitHub and GitLab describe the command as experimental, a designation signaling that the interface may still change before it is stabilized.
Config-based hooks simplify shared repository setups
Another feature that first appeared in Git 2.54 and now ships with parallel execution is configuration-based hooks. Historically, sharing Git hooks across multiple repositories required either a third-party hook manager or manually symlinking scripts into each repository’s $GIT_DIR/hooks directory, a process that was tedious and prone to errors.
With the 2.54 release, users gained the ability to specify hooks directly in configuration files, simplifying management of shared hook behavior at the user, system, or repository level.
Config-based hooks can now run compatible hooks in parallel, controlled by job settings, while hooks that need shared state still run serially. Combined with that opt-in parallelism, teams can define a shared suite of checks once in a user- or system-level config file, push that config across their organization, and let Git run those checks simultaneously without any third-party hook manager in the middle.
It is the kind of quality-of-life improvement that does not change what Git can do but meaningfully reduces the overhead of keeping a team’s repository hygiene consistent.
A path toward Git 3.0
Up to now in the Git world, Git’s Rust code has been opt-in at build-time and optional. With Git 2.55, the Rust code is still optional but is now enabled by default. Git 2.55 will build with Rust support enabled by default unless opting out with the NO_RUST option. Git 3.0, or some later point, is when Git’s Rust support may become mandatory.
Like most Git releases, the bulk of 2.55 is invisible: faster packing, less memory in the diff engine, and groundwork for the ongoing move to Rust.
Git 2.54 drew features and bug fixes from over 137 contributors, 66 of them new , a contributor count that reflects the project’s continued health as one of the most widely deployed pieces of open-source infrastructure in the software industry.
The project underpins virtually every major code-hosting platform, from GitHub to GitLab, and its releases ripple outward to every developer environment that packages it, from Linux distributions to macOS via Homebrew to Windows via Git for Windows.
Full release notes for Git 2.55 are available on the GitHub Blog and on the GitLab Blog.
