Installer git-delete-merged-branches avec Homebrew, apt, Nix

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• git-dmb

Historique du projet

The upstream Git history begins in July 2020 with code for version 1.0.0. The project advanced quickly through early releases and later settled into a maintained CLI with tests, pre-commit integration, and package-manager distribution.

The README frames the tool around safe cleanup rather than raw deletion. It detects multiple forms of de-facto merges, including rebase merges, squash merges with extra effort, and cherry-picks by leveraging `git cherry`; it also supports workflows with multiple release branches.

Historique d'adoption

The official README lists install paths through pip and distribution packages including Arch AUR, Debian, Gentoo, Homebrew, MacPorts, NixOS, Ubuntu, and Void Linux. That makes the tool visible in the same package-manager space as Git workflow helpers rather than only as a Python package.

Its README also documents a command-name clash with git-extras, whose utility collection ships a simpler `git-delete-merged-branches` script. The standalone project responds by offering `python3 -m git_delete_merged_branches` and `git-dmb` invocation paths.

Modes d'utilisation

Practitioners run it inside a repository to update remotes, fast-forward tracked release branches, list local and remote branches that appear merged, and ask before deletion. A `--dry-run` mode lets users inspect actions first, and `--verbose` shows Git commands.

The tool is used when teams accumulate topic branches across local clones, forks, and remote hosts. It is provider-agnostic and documents use with GitHub, GitLab, Gitea, and other Git hosting because it works through Git commands rather than a hosting API.

Pourquoi les passionnés de paquets s'y intéressent

The package is a good example of a small workflow CLI whose value lies in guardrails: branch deletion is risky, so the project packages conservative prompts, dry runs, `--force-with-lease`, and no shell-command construction.

Its overlap with git-extras is package-manager-relevant because PATH order can decide which command a user runs when both packages are installed.

Chronologie

• 2020: The repository begins with version 1.0.0 code.
• 2020: Rapid 1.x through 6.x releases establish the CLI and packaging shape.
• 2021: Version 6.4.0 continues the maintained Python CLI line.
• 2022: Version 7.4.0 lands after several 7.x releases.
• 2025: Version 7.5.0 is released.
• 2026: Version 7.6.0 is released.

Related projects

• git-extras is a related utility collection and a direct command-name conflict noted by the README.
• GitHub's automatic deletion of branches for merged pull requests is mentioned as a complementary hosting-side cleanup feature.
• `git cherry` is the Git command named by the README as part of merge-detection logic.

Sources

• https://formulae.brew.sh/formula/git-delete-merged-branches documents Homebrew packaging.
• https://github.com/hartwork/git-delete-merged-branches documents installation, examples, features, safety rules, best practices, and the git-extras command-name clash.
• https://github.com/hartwork/git-delete-merged-branches/releases documents release progression.