A modern TypeScript CLI for managing multi-repository projects. Execute commands across multiple git repositories simultaneously.
- Clone entire project ecosystems with one command
- Execute arbitrary commands across all repositories
- Parallel or sequential execution modes
- Flexible filtering (include/exclude by name or pattern)
- NPM operations across all projects
- Symlink projects for local development
- JSON and YAML configuration formats
- Multiple config files with
-fflag (like Docker Compose)
npm install -g @dafish/gogo-metaOr run without installing:
npx @dafish/gogo-meta --helpdocker pull ghcr.io/dafish/gogo-metaWhen using Docker, mount your working directory and SSH keys so gogo can access your repositories:
docker run -it --rm \
-v "$PWD":/workspace \
-v "$HOME/.ssh":/root/.ssh:ro \
-w /workspace \
ghcr.io/dafish/gogo-meta <command>Any gogo command shown in this README can be run via Docker by replacing gogo with the docker run call above. For convenience, you can create a shell alias:
alias gogo='docker run -it --rm -v "$PWD":/workspace -v "$HOME/.ssh":/root/.ssh:ro -w /workspace ghcr.io/dafish/gogo-meta'git clone https://github.com/daFish/gogo-meta.git
cd gogo-meta
bun install
bun run build
bun link# Initialize a new meta repository
gogo init
# Import existing repositories
gogo project import api git@github.com:org/api.git
gogo project import web git@github.com:org/web.git
# Clone a meta repository (includes all children)
gogo git clone git@github.com:org/meta-repo.git
# Run commands across all projects
gogo exec "npm install"
gogo exec "git status" --parallelThe config file defines child repositories, ignore patterns, and predefined commands. Both JSON and YAML formats are supported.
gogo looks for config files in the following order of precedence: .gogo (JSON) > .gogo.yaml > .gogo.yml. The first file found is used.
{
"projects": {
"api": "git@github.com:org/api.git",
"web": "git@github.com:org/web.git",
"libs/shared": "git@github.com:org/shared.git"
},
"ignore": [".git", "node_modules", ".vagrant", ".vscode"],
"commands": {
"build": "npm run build",
"test": {
"cmd": "npm test",
"parallel": true,
"description": "Run tests in all projects"
},
"deploy": {
"cmd": "npm run deploy",
"parallel": true,
"concurrency": 2,
"includeOnly": ["api", "web"]
}
}
}# Main services
projects:
api: git@github.com:org/api.git
web: git@github.com:org/web.git
libs/shared: git@github.com:org/shared.git
ignore:
- .git
- node_modules
- .vagrant
- .vscode
# Predefined commands
commands:
build: npm run build
test:
cmd: npm test
parallel: true
description: Run tests in all projects
deploy:
cmd: npm run deploy
parallel: true
concurrency: 2
includeOnly:
- api
- webFor large projects you can split configuration across multiple files and merge them at runtime using the -f, --file flag:
# Load primary .gogo plus additional projects from .gogo.devops
gogo -f .gogo.devops exec "npm test"
# Multiple overlays are applied in order
gogo -f .gogo.devops -f .gogo.extra git statusOverlay files follow the same format as the primary config (JSON or YAML). When merging:
- Projects: overlay entries are added; on key conflict the overlay wins
- Ignore: arrays are concatenated and deduplicated
- Commands: overlay entries are added; on key conflict the overlay wins
Overlay paths are resolved relative to the directory containing the primary config file.
Write commands (project create, project import) only modify the primary config file — overlay projects are never absorbed into it.
These options are available for most commands:
| Option | Description |
|---|---|
-f, --file <path> |
Additional config file to merge (repeatable) |
--include-only <dirs> |
Only target specified directories (comma-separated) |
--exclude-only <dirs> |
Exclude specified directories (comma-separated) |
--include-pattern <regex> |
Include directories matching regex pattern |
--exclude-pattern <regex> |
Exclude directories matching regex pattern |
--parallel |
Execute commands concurrently |
--concurrency <n> |
Maximum parallel processes (default: 4) |
Initialize a new gogo-meta repository by creating a config file.
gogo init # Create .gogo (JSON, default)
gogo init --format yaml # Create .gogo.yaml (YAML)
gogo init --force # Overwrite existing config file| Option | Description |
|---|---|
-f, --force |
Overwrite existing config file |
--format <format> |
Config file format: json (default) or yaml |
Execute an arbitrary command in all project directories.
# Run in each project sequentially
gogo exec "npm test"
# Run in parallel
gogo exec "npm install" --parallel
# Run with limited concurrency
gogo exec "npm run build" --parallel --concurrency 2
# Filter to specific projects
gogo exec "git status" --include-only api,web
# Exclude projects
gogo exec "npm install" --exclude-only docs
# Use regex patterns
gogo exec "npm test" --include-pattern "^libs/"| Option | Description |
|---|---|
--include-only <dirs> |
Only run in specified directories |
--exclude-only <dirs> |
Skip specified directories |
--include-pattern <regex> |
Include directories matching pattern |
--exclude-pattern <regex> |
Exclude directories matching pattern |
--parallel |
Run commands concurrently |
--concurrency <n> |
Max parallel processes |
Run a predefined command from the .gogo file.
# List available commands
gogo run
gogo run --list
# Run a predefined command
gogo run build
# Override config options with CLI flags
gogo run test --parallel
gogo run deploy --include-only api
# Commands can define defaults in .gogo:
# - parallel: true/false
# - concurrency: number
# - includeOnly/excludeOnly: array of directories
# - includePattern/excludePattern: regex patterns
# CLI flags override these config defaults| Option | Description |
|---|---|
-l, --list |
List all available commands |
--include-only <dirs> |
Only run in specified directories (overrides config) |
--exclude-only <dirs> |
Skip specified directories (overrides config) |
--include-pattern <regex> |
Include directories matching pattern (overrides config) |
--exclude-pattern <regex> |
Exclude directories matching pattern (overrides config) |
--parallel |
Run commands concurrently (overrides config) |
--concurrency <n> |
Max parallel processes (overrides config) |
Clone a meta repository and all its child repositories.
# Clone to directory matching repo name
gogo git clone git@github.com:org/meta-repo.git
# Clone to custom directory
gogo git clone git@github.com:org/meta-repo.git -d my-project| Option | Description |
|---|---|
-d, --directory <dir> |
Target directory name |
Clone any child repositories defined in .gogo that don't exist locally.
gogo git update
gogo git update --parallel
gogo git update --include-only api,web| Option | Description |
|---|---|
--include-only <dirs> |
Only update specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Clone in parallel |
--concurrency <n> |
Max parallel clones |
Show git status across all repositories.
gogo git status
gogo git status --parallel
gogo git status --include-only api| Option | Description |
|---|---|
--include-only <dirs> |
Only check specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Run in parallel |
Pull changes in all repositories.
gogo git pull
gogo git pull --parallel| Option | Description |
|---|---|
--include-only <dirs> |
Only pull specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Pull in parallel |
--concurrency <n> |
Max parallel pulls |
Push changes in all repositories.
gogo git push
gogo git push --include-only api,web| Option | Description |
|---|---|
--include-only <dirs> |
Only push specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Push in parallel |
List, create, or delete branches across all repositories.
# List branches
gogo git branch
# List all branches (including remote)
gogo git branch --all
# Create a new branch
gogo git branch feature/new-feature
# Delete a branch
gogo git branch feature/old-feature --delete| Option | Description |
|---|---|
-d, --delete |
Delete the specified branch |
-a, --all |
List all branches (local and remote) |
--include-only <dirs> |
Only target specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Run in parallel |
Checkout a branch in all repositories.
# Checkout existing branch
gogo git checkout main
# Create and checkout new branch
gogo git checkout -b feature/new-feature| Option | Description |
|---|---|
-b, --create |
Create the branch if it doesn't exist |
--include-only <dirs> |
Only target specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Run in parallel |
Commit changes in all repositories with the same message.
gogo git commit -m "Update dependencies"
gogo git commit -m "Fix bug" --include-only api| Option | Description |
|---|---|
-m, --message <msg> |
Commit message (required) |
--include-only <dirs> |
Only commit in specified projects |
--exclude-only <dirs> |
Skip specified projects |
Create and initialize a new child repository.
gogo project create libs/new-lib git@github.com:org/new-lib.gitThis will:
- Create the directory
- Initialize git
- Add the remote origin
- Add the project to
.gogo - Add the path to
.gitignore
Import an existing repository as a child project.
# Clone and import a remote repository
gogo project import api git@github.com:org/api.git
# Import an existing local directory (reads remote from git)
gogo project import existing-folder
# Register without cloning (clone later with gogo git update)
gogo project import api git@github.com:org/api.git --no-clone| Option | Description |
|---|---|
--no-clone |
Register project in .gogo without cloning |
This will:
- Clone the repository (if URL provided and directory doesn't exist, unless
--no-clone) - Add the project to
.gogo - Add the path to
.gitignore(unless--no-clone)
Run npm install in all projects.
gogo npm install
gogo npm i # Alias
gogo npm install --parallel| Option | Description |
|---|---|
--include-only <dirs> |
Only install in specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Run in parallel |
--concurrency <n> |
Max parallel installs |
Run npm ci in all projects (clean install from lockfile).
gogo npm ci
gogo npm ci --parallel| Option | Description |
|---|---|
--include-only <dirs> |
Only run in specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Run in parallel |
--concurrency <n> |
Max parallel processes |
Create npm links between projects for local development.
# Create global npm links for all projects
gogo npm link
# Create symlinks between all interdependent projects
gogo npm link --all| Option | Description |
|---|---|
--all |
Link all projects bidirectionally (symlink dependencies) |
--include-only <dirs> |
Only link specified projects |
--exclude-only <dirs> |
Skip specified projects |
Run an npm script in all projects.
# Run in all projects
gogo npm run build
# Run in parallel
gogo npm run test --parallel
# Only run if script exists
gogo npm run lint --if-present| Option | Description |
|---|---|
--if-present |
Only run if the script exists in package.json |
--include-only <dirs> |
Only run in specified projects |
--exclude-only <dirs> |
Skip specified projects |
--parallel |
Run in parallel |
--concurrency <n> |
Max parallel processes |
Validate your configuration. This runs two checks:
- Config files — every
.gogo/.gogo.*file in the current directory is parsed and checked against its schema. - Working copy — each project declared in the resolved config must have a matching directory on disk.
If a configured project directory is missing, validation fails with a hint:
run gogo migrate if the project was moved/renamed in the config, or
gogo git update to clone a project that has not been cloned yet.
gogo validateReconcile the working copy with the configuration. After you re-arrange project
paths in .gogo (rename or move entries while keeping the same repository URL),
gogo migrate finds each repository at its current location and moves it to the
path declared in the config. Repositories are matched by their origin remote
URL, so renames and moves are detected automatically. Empty parent directories
left behind by a move are removed.
gogo migrate # Apply the moves
gogo migrate --dry-run # Show what would move without changing anythingBehavior:
- In sync — a repository already at its configured path is left untouched.
- Moved/renamed — a repository found at a different path is moved to match.
- Conflict — if the target path is occupied by a different repository, migration aborts without touching anything.
- Missing — a configured repository that is not present anywhere in the
working copy is reported; run
gogo git updateto clone it.
| Option | Description |
|---|---|
--dry-run |
Show what would be moved without making any changes |
mkdir my-project && cd my-project
gogo init
gogo project import backend git@github.com:org/backend.git
gogo project import frontend git@github.com:org/frontend.git
gogo project import shared git@github.com:org/shared.git
gogo npm install --parallel# Start of day: pull all changes
gogo git pull --parallel
# Check status across all repos
gogo git status
# Create feature branch everywhere
gogo git checkout -b feature/my-feature
# Run tests
gogo npm run test --parallel
# Commit changes
gogo git commit -m "Add feature"
# Push changes
gogo git push# Only work with API and shared libs
gogo exec "npm test" --include-only api,libs/shared
# Exclude documentation from builds
gogo npm run build --exclude-only docs
# Target all libs
gogo git status --include-pattern "^libs/"- npm install: Node.js 24 or higher, Git
- Docker: Docker
- From source: Bun 1.x or higher, Git
MIT