# git-imerge mit Homebrew, apt, dnf, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für git-imerge in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:git-imerge
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install git-imerge
```

  Evidenz: local Homebrew formula metadata

### Linux

- Debian apt (92%):

```sh
sudo apt install git-imerge
```

  Evidenz: Debian stable package indexes: git-imerge from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- dnf (92%):

```sh
sudo dnf install git-imerge
```

  Evidenz: Fedora Rawhide package metadata: git-imerge from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst

- Nix (92%):

```sh
nix profile install nixpkgs#git-imerge
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/gi/git-imerge/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:git-imerge
- **Paketmanager:** Homebrew
- **Version:** 1.2.0
- **Quellzusammenfassung:** Incremental merge for git
- **Homepage:** <https://github.com/mhagger/git-imerge>
- **Repository:** <https://github.com/mhagger/git-imerge>
- **Zuletzt aktualisiert:** 2026-06-18T09:25:51+09:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- git-imerge (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.2.0
## Projektgeschichte und Nutzung

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.

### Projektgeschichte

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.

### Adoptionsgeschichte

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.

### Wie es verwendet wird

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.

### Warum Paket-Nerds sich dafür interessieren

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.

### Zeitleiste

- 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.

### Quellen

- <https://api.github.com/repos/mhagger/git-imerge/releases>
- <https://github.com/mhagger/git-imerge>
- <https://raw.githubusercontent.com/mhagger/git-imerge/master/README.md>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals

## Andere Paketmanager-Einträge

- Debian apt - git-imerge - 1.2.0-5: normalized package name match | Debian stable package indexes: git-imerge from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | incremental merge and rebase for git | https://github.com/mhagger/git-imerge
- Nix - git-imerge: normalized package name match | nixpkgs package indexes: pkgs/by-name/gi/git-imerge/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - git-imerge - 1.2.0-5: normalized package name match | Ubuntu 24.04 LTS package indexes: git-imerge from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | incremental merge and rebase for git | https://github.com/mhagger/git-imerge
- dnf - git-imerge - 1.2.0-4.fc45: normalized package name match | Fedora Rawhide package metadata: git-imerge from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Incremental merge and rebase for Git | https://github.com/mhagger/git-imerge


## Combined YAML source

View the package source record on GitHub. [combined/git-imerge.yml](https://github.com/mxcl/pkgdb/blob/main/combined/git-imerge.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph