使用 Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper 安装 git-extras

项目链接

• 主页

命令和别名

• git-abort
• git-alias
• git-archive-file
• git-authors
• git-browse
• git-browse-ci
• git-brv
• git-bulk
• git-changelog
• git-clear
• git-clear-soft
• git-coauthor
• git-commits-since
• git-continue
• git-contrib
• git-count
• git-cp
• git-create-branch
• git-delete-branch
• git-delete-merged-branches
• git-delete-squashed-branches
• git-delete-submodule
• git-delete-tag
• git-delta
• git-effort
• git-extras
• git-feature
• git-force-clone
• git-fork
• git-fresh-branch
• git-get
• git-gh-pages

项目历史

The repository began in August 2010 under TJ Holowaychuk. Early commits and 0.0.x tags established the project's pattern: many small `git-*` executables installed so Git can dispatch them as `git <name>` subcommands.

The project reached 1.0.0 in February 2012 and continued through major release lines over the following decade. Its command set grew into dozens of utilities documented in `Commands.md`, including `git summary`, `git feature`, `git changelog`, `git effort`, `git ignore`, `git release`, `git undo`, and branch-cleanup helpers.

Version 6.4 in 2022 changed the assumed default branch from `master` to `main` while leaving configuration overrides through `git-extras.default-branch` or Git's `init.defaultBranch`. That change reflects how the project tracks common Git hosting conventions while preserving user configuration.

采用历史

git-extras is packaged broadly enough to appear in Homebrew, Debian and Ubuntu, Fedora-family distributions, MacPorts, Nix, Arch-family repositories, and other package-manager indexes represented in the input metadata.

Its ecosystem role is partly cultural: before every team had bespoke Git aliases, shell snippets, and hosted pull-request tools, git-extras collected common shell workflows into named Git subcommands with man pages and completions.

使用方式

Practitioners install the package and then run commands through Git's subcommand mechanism, for example `git summary`, `git feature`, `git changelog`, `git release`, `git ignore`, `git undo`, or `git delete-merged-branches`.

Some commands read or write Git configuration in `.git/config` or `~/.gitconfig`; the README documents branch-name defaults through `git-extras.default-branch` and `init.defaultBranch`. The package is therefore often used as a personal workflow layer on top of plain Git.

为什么软件包爱好者会关心

git-extras matters because it is a package of shell-level affordances rather than a single tool. It demonstrates Git's command-discovery design: any executable named `git-foo` on PATH can become `git foo`.

It also creates package-manager edge cases. Some commands overlap with standalone tools, including the `git-delete-merged-branches` name clash documented by the standalone branch-cleanup project.

时间线

• 2010: The repository begins and 0.0.x tags are released.
• 2012: Version 1.0.0 is released.
• 2014: Version 2.x releases continue expanding the command collection.
• 2015: Versions 3.0.0 and 4.0.0 are released.
• 2020: Version 6.0.0 is released.
• 2022: Version 6.4.0 changes the assumed default branch name to `main`.
• 2023: Version 7.0.0 is released.
• 2026: Version 7.5.0 is released.

Related projects

• Git itself is the host command framework that discovers git-extras executables.
• hub, gh, diff-so-fancy, delta, and standalone branch-cleanup tools occupy adjacent Git workflow-helper territory.
• git-delete-merged-branches is directly related because both packages can provide a command with the same name.

来源

• https://formulae.brew.sh/formula/git-extras documents Homebrew packaging.
• https://github.com/tj/git-extras documents the README, installation, command list, default-branch behavior, and contribution workflow.
• https://github.com/tj/git-extras/blob/master/Commands.md documents the command surface.
• https://github.com/tj/git-extras/blob/master/History.md documents release history.