# git-when-merged を Homebrew, MacPorts, Nix でインストール

git-when-merged のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:git-when-merged
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install git-when-merged
```

  証拠: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install git-when-merged
```

  証拠: MacPorts ports tree: devel/git-when-merged/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#git-when-merged
```

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

## パッケージ情報

- **パッケージキー:** brew:git-when-merged
- **パッケージマネージャ:** Homebrew
- **バージョン:** 1.2.1
- **ソース概要:** Find where a commit was merged in git
- **ホームページ:** <https://github.com/mhagger/git-when-merged>
- **リポジトリ:** <https://github.com/mhagger/git-when-merged>
- **最終更新:** 2026-06-18T09:25:51+09:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- git-when-merged (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 1.2.1
## プロジェクトの歴史と使われ方

git-when-merged is a Python Git extension that finds the merge commit that first brought a given commit into a branch.

### プロジェクトの歴史

Michael Haggerty created the repository in February 2013. The README says the command was originally based on a Stack Overflow suggestion for finding the merge commit that included a specific commit.

The project grew around Git-history forensics. The 2016 releases added recursive merge tracing, log output, commit-only output, branch display, and describe-based options. A 2022 release added the packaging work needed for PyPI distribution.

### 採用の歴史

The README documents several installation paths: pipx from PyPI, a local virtual environment, cloning the repository onto PATH, and Homebrew for macOS users. Package-manager metadata also lists distribution through Homebrew, MacPorts, and Nix.

### 使われ方

Practitioners use git when-merged during code archaeology, release maintenance, and regression tracking. It walks first-parent history to answer when and why a commit entered a branch, with options to show logs, diffs, merge ranges, patterns, and configured reference groups.

### パッケージ好きにとっての重要性

The tool is a package-nerd favorite because it wraps a subtle Git graph question in a memorable subcommand, making first-parent merge analysis scriptable and repeatable.

### タイムライン

- 2013: Repository created.
- 2016: v1.1 and v1.2 releases expanded merge-analysis options.
- 2022: v1.2.1 added PyPI release packaging.

### Related projects

- git log --first-parent, git describe, pipx, PyPI, Homebrew

### ソース

- <https://formulae.brew.sh/formula/git-when-merged>
- <https://github.com/mhagger/git-when-merged>
- <https://github.com/mhagger/git-when-merged/releases>
- <https://pypi.org/project/git-when-merged>
- <https://raw.githubusercontent.com/mhagger/git-when-merged/master/README.md>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals

## 他のパッケージマネージャ記録

- Nix - git-when-merged: normalized package name match | nixpkgs package indexes: pkgs/by-name/gi/git-when-merged/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- MacPorts - git-when-merged: normalized package name match | MacPorts ports tree: devel/git-when-merged/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

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


## ソース

- 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