# git-multipush mit Homebrew installieren

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

## Installation

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

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install git-multipush
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:git-multipush
- **Paketmanager:** Homebrew
- **Version:** 2.3
- **Quellzusammenfassung:** Push a branch to multiple remotes in one command
- **Homepage:** <https://github.com/gavinbeatty/git-multipush>
- **Repository:** <https://github.com/gavinbeatty/git-multipush>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- git-multipush (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

git-multipush is a small Git extension for pushing one branch to several remotes with one command. Its README frames the tool around a 2010 multi-forge workflow, naming GitHub, Gitorious, and repo.or.cz as examples of places where the same repository might be hosted.

### Projektgeschichte

Gavin Beatty published git-multipush as a POSIX shell-oriented Git subcommand with a generated manpage and a traditional Makefile install path. GitHub records the repository creation on 2010-02-04, and the README copyright and first tag both point to 2010 as the initial public period.

### Adoptionsgeschichte

The project stayed niche, but it entered Homebrew as a formula, which made it easy for macOS and Linuxbrew users to install a Git extension that otherwise followed a classic source-install workflow. GitHub metadata records a small public audience rather than broad ecosystem adoption.

### Wie es verwendet wird

Practitioners use git-multipush when they maintain the same branch on several Git remotes. The command can push to explicit remotes, save per-branch remote lists in Git config, print configured remotes, run dry runs, and choose whether a failed push stops the whole operation or is reported after other pushes have been attempted.

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

The package is a snapshot of early distributed-forge Git habits: before one forge dominated many workflows, developers often mirrored projects across several hosts. As a package, it is interesting because it wraps Git config and git-push without adding a service dependency.

### Zeitleiste

- 2010: Repository and first public tag appeared on GitHub.
- 2010: v2.3 and v2.4 release-candidate tags followed during early iteration.
- 2020: Repository activity included a push after the early release period.

### Related projects

- git-push
- Git remote configuration
- Homebrew formulae for Git extensions

### Quellen

- <https://formulae.brew.sh/formula/git-multipush>
- <https://github.com/gavinbeatty/git-multipush>
- <https://raw.githubusercontent.com/gavinbeatty/git-multipush/main/README.mkd>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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


## Combined YAML source

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


## Quellen

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