# 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 ```sh sudo av install brew:git-multipush ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install git-multipush ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:git-multipush - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.3 - **Source summary:** Push a branch to multiple remotes in one command - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** GPL-3.0-or-later - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - git-multipush (cli) - git-multipush (alias) ## Build dependencies - asciidoc ## Install behavior - Post-install hook: not defined - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.3 - Local data: ok - Upstream repository: https://github.com/gavinbeatty/git-multipush - info: No package-manager update timestamp was available. - info: No cached GitHub release or tag data was available. ## 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 Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** git-multipush - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [asciidoc](https://www.automicvault.com/pkg/brew/asciidoc/) - Build dependency declared by Homebrew. - [git-machete](https://www.automicvault.com/pkg/brew/git-machete/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, git-workflow. - [git-now](https://www.automicvault.com/pkg/brew/git-now/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, git-workflow. - [git-number](https://www.automicvault.com/pkg/brew/git-number/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, git-workflow. - [git-lfs](https://www.automicvault.com/pkg/brew/git-lfs/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, version-control. - [git-mediate](https://www.automicvault.com/pkg/brew/git-mediate/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, version-control. - [git-octopus](https://www.automicvault.com/pkg/brew/git-octopus/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, version-control. - [git-open](https://www.automicvault.com/pkg/brew/git-open/) - Shares av.db curated category or tags: cli, developer-tools, git, git-extension, version-control. - [aicommit](https://www.automicvault.com/pkg/brew/aicommit/) - Shares av.db curated category or tags: cli, developer-tools, git, version-control. ## Combined YAML source View the package source record on GitHub. [combined/git-multipush.yml](https://github.com/automic-vault/db/blob/main/combined/git-multipush.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph