# Installer multi-gitter avec Homebrew, MacPorts, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de multi-gitter pour les workflows d'agents IA.

## installation

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

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

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

  Preuve: local Homebrew formula metadata

- MacPorts (94%):

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

  Preuve: 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
```

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

## Faits du paquet

- **Clé du paquet:** brew:multi-gitter
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.63.1
- **Résumé source:** Update multiple repositories in with one command
- **Page d'accueil:** <https://github.com/lindell/multi-gitter>
- **Dépôt:** <https://github.com/lindell/multi-gitter>
- **Dernière mise à jour:** 2026-07-29T17:05:01+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- multi-gitter (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 0.63.1
## Historique du projet et usages

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.

### Modes d'utilisation

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>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour multi-gitter. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.


## Autres enregistrements de gestionnaires de paquets

- 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