# Install multi-gitter with Homebrew, MacPorts, scoop

Update multiple repositories in with one command. Version 0.63.1 via Homebrew; verified 2026-07-29. Also installable with macports: sudo port install multi-gitter.

## Install

```sh
sudo av install brew:multi-gitter
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install multi-gitter
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install multi-gitter
```

  Evidence: MacPorts ports tree: devel/multi-gitter/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Windows

- Scoop (92%):

```sh
scoop install main/multi-gitter
```

  Evidence: Scoop official bucket manifest trees: bucket/multi-gitter.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:multi-gitter
- **Package manager:** Homebrew
- **Version:** 0.63.1
- **Source summary:** Update multiple repositories in with one command
- **Homepage:** <https://github.com/lindell/multi-gitter>
- **Repository:** <https://github.com/lindell/multi-gitter>
- **Last updated:** 2026-07-29T17:05:01+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- multi-gitter (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.63.1
## Project history and usage

multi-gitter is a Go command-line tool from the lindell/multi-gitter project for making the same scripted change across many Git repositories. Its README frames the core workflow as running any script or program inside each selected repository, then creating pull requests wherever the script changed files; it also supports manual merging or automatic merging after CI succeeds. The project fits the multi-repository maintenance niche that grew around microservices and internal shared libraries: dependency bumps, pull-request-template synchronization, search-and-replace edits, lint fixes, and mechanical refactors that would be tedious to apply repository by repository.

### How it is used

In practice, users point multi-gitter at an organization, user, or explicit repository list, provide a branch name and commit message, and let their own Bash, Python, Node.js, Go, or other script do the actual edit. That keeps the tool narrower than a refactoring framework: it handles checkout, fan-out, commits, pull requests, reviewer/CI integration, and provider tokens, while users keep using ordinary scripts for the content change. Its package-manager niche is a developer-automation CLI distributed through Homebrew, MacPorts, and Scoop, useful for teams that chose many repositories instead of a monorepo.

### Sources

- <https://dev.to/lindell/make-bulk-changes-over-multiple-repositories-27i9>
- <https://formulae.brew.sh/formula/multi-gitter>
- <https://github.com/lindell/multi-gitter>


## Security Notes

No matching local secret-handling manifest was found for multi-gitter. Nucleus package metadata is still published here so future coverage has a stable package URL.


## Other Package-Manager Records

- MacPorts - multi-gitter: normalized package name match | MacPorts ports tree: devel/multi-gitter/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Scoop - main/multi-gitter: normalized package name match | Scoop official bucket manifest trees: bucket/multi-gitter.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

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


## Sources

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