macOS
Homebrewverified · 100%
brew install git-multipushlocal Homebrew formula metadata
brew / rank 15018
Install git-multipush with Homebrew
Push a branch to multiple remotes in one command. Version 2.3 via Homebrew; verified from local package data.
install
Additional install commands
overview
Package summary
Push a branch to multiple remotes in one command
Project links
Commands and aliases
- git-multipush
history
Project history and usage
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.
Project history
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.
Adoption history
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.
How it is used
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.
Why package nerds care
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.
Timeline
- 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
Sources
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
git-multipush | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version2.3
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:git-multipush |
|---|---|
| Version | 2.3 |
| Package manager | Homebrew |
| Homepage | https://github.com/gavinbeatty/git-multipush |
| Repository | https://github.com/gavinbeatty/git-multipush |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- pkg.so package database
- pkgdb category and tag curation