macOS
Homebrewverified · 100%
brew install git-imergelocal Homebrew formula metadata
brew / rank 7586
Install git-imerge with Homebrew, apt, dnf, Nix
Incremental merge for git. Version 1.2.0 via Homebrew; verified 2026-06-18. Also installable with debian: sudo apt install git-imerge.
install
Additional install commands
Linux
Debian aptverified · 92%
sudo apt install git-imergeDebian stable package indexes · git-imerge · source: deb.debian.org
Fedora dnfverified · 92%
sudo dnf install git-imergeFedora Rawhide package metadata · git-imerge · source: dl.fedoraproject.org
Nixverified · 92%
nix profile install nixpkgs#git-imergenixpkgs package indexes · pkgs/by-name/gi/git-imerge/package.nix · source: api.github.com
overview
Package summary
Incremental merge for git
Project links
Commands and aliases
- git-imerge
history
Project history and usage
git-imerge is a Git extension for incremental merge, rebase, revert, and drop operations. It breaks large conflict sets into smaller pairwise conflicts and records progress inside Git refs so work can be paused, tested, shared, and resumed.
Project history
Michael Haggerty's repository was created in May 2013, the same period in which the README points users to a GitMerge 2013 presentation and a practical introduction article. The project framed incremental merging as a way to reduce conflict pain by identifying exactly which commits from two branches conflict.
Adoption history
git-imerge became a well-known specialist tool among advanced Git users because it addressed a real pain point in long-running branches: merge conflicts that are too large to understand at once. Its GitHub repository has thousands of stars and its packaging spans Homebrew, Debian, Fedora, Nix, and Ubuntu, indicating durable interest beyond a single distribution.
How it is used
Practitioners use commands such as `git-imerge merge BRANCH`, `git-imerge rebase BRANCH`, and `git-imerge continue` as analogues to Git's native merge and rebase workflows. During an operation, git-imerge records state under `refs/imerge/NAME`, can show a diagram of progress, and can simplify the final result into a merge, rebase, history-preserving rebase, or fuller intermediate history.
Why package nerds care
The package is notable because it is not a wrapper around a single Git porcelain command; it stores its own operation graph in Git's object database and refs. That makes it especially interesting to people who study Git internals, conflict resolution, and packaging of Git subcommands.
Timeline
- 2013: GitHub repository created and GitMerge 2013 presentation referenced by the README.
- 2016: Release v1.0.0 published.
- 2018: Release v1.1.0 published.
- 2020: Release v1.2.0 published.
Related projects
- git-imerge builds on Git's merge, rebase, rerere, refs, and object storage. It is related in spirit to conflict-reuse and history-preserving workflows rather than to ordinary visual merge tools.
Sources
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
git-imerge | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.2.0
manager updated2026-06-18
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:git-imerge |
|---|---|
| Version | 1.2.0 |
| Package manager | Homebrew |
| Homepage | https://github.com/mhagger/git-imerge |
| Repository | https://github.com/mhagger/git-imerge |
| Last updated | 2026-06-18T09:25:51+09:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Debian apt95%
git-imerge 1.2.0-5
incremental merge and rebase for git
https://github.com/mhagger/git-imerge
sudo apt install git-imerge- Section: vcs
- Architecture: all
- 2 dependencies
- 2 optional deps
- normalized package name match
- Matched by: Git Imerge
Nix95%
git-imerge
nix profile install nixpkgs#git-imerge- normalized package name match
- Matched by: Git Imerge
Ubuntu apt95%
git-imerge 1.2.0-5
incremental merge and rebase for git
https://github.com/mhagger/git-imerge
sudo apt install git-imerge- Section: universe/vcs
- Architecture: all
- 2 dependencies
- 2 optional deps
- normalized package name match
- Matched by: Git Imerge
dnf95%
git-imerge 1.2.0-4.fc45
Incremental merge and rebase for Git
https://github.com/mhagger/git-imerge
sudo dnf install git-imerge- License: GPL-2.0-or-later
- Category: Unspecified
- Architecture: noarch
- Source Package: git-imerge
- 3 dependencies
- 3 provides
- normalized package name match
- Matched by: Git Imerge
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation