Run common Git commands across many repositories — safely and simply.

gitbatch is a lightweight Go CLI designed to execute git status, git diff --no-pager, git pull, git add, git commit, and git push across multiple repositories using glob patterns.

I built this tool because, while working with clients who had multiple websites with similar structures, I constantly found myself repeating the same Git commands across many clones. Often, I needed to make a change that affected all these repositories. gitbatch helps automate these repetitive tasks while keeping them safe and predictable.

• Safe: Avoid running commands in non-repositories. Destructive operations like push --force require confirmation.
• Simple: Small, predictable CLI with explicit flags.
• Reliable repository detection: Uses git rev-parse --is-inside-work-tree instead of just checking for a .git folder.
• Interactive confirmation for dangerous commands: Pushes prompt for confirmation by default to prevent mass accidents.
• Globbing with doublestar: Enables recursive patterns like projects/**/microservice-* across platforms.
• Built with Cobra: Subcommands, flags, and help messages follow familiar patterns, making the CLI intuitive and easy to extend.
• Streamed output & timeouts: See logs/errors per repository immediately. Commands have sane timeouts to prevent hangs.

With Go installed, run:

# Install the latest version
go install github.com/patrickkdev/gitbatch@latest

This places the gitbatch binary in $GOPATH/bin or $GOBIN.

All commands accept one or more path patterns (globs). Only directories detected as Git repositories are processed.

Runs git status in each repository.

Why: Quickly check the state of multiple working trees (uncommitted changes, untracked files, current branches) before pulling or committing.

Runs git --no-pager diff in each repository.

Why: Inspect differences across repositories without opening an editor. Useful for validating changes before committing.

Runs git pull in each repository.

Why: Automates fetching and merging from remotes across multiple clones. It respects each repo’s configured merge strategy and remote.

Runs git add -- <pathspec> in each repository. Defaults to . if no pathspec is provided.

Why: Encourages safe, targeted additions. Using -- and explicit pathspecs prevents accidentally adding unrelated files.

Tip: Use explicit pathspecs for large projects or nested structures to avoid unintended changes.

Runs git commit -m "message" in each repository. Skips repos with nothing to commit.

Why: Batch commits with a consistent message across multiple repos. Avoids interactive commit prompts, keeping automation-friendly behavior.

Runs git push in each repository.

• Prompts for confirmation by default.
• Use --yes to skip confirmation.
• Use --force with caution.

Why: Pushing changes is impactful. Confirmation helps prevent accidental mass updates to remotes.

# Show status for multiple repositories
gitbatch status ./projects/*

# See diffs recursively
gitbatch diff "projects/**/service-*"

# Add JS files across repos
gitbatch add -p "src/**/*.js" repos/*

# Commit with a message
gitbatch commit -m "chore: bump deps" repos/*

# Push with confirmation
gitbatch push repos/*

# Skip push confirmation
gitbatch push --yes repos/*

# Force push (use with caution!)
gitbatch push --yes --force repos/*

Tip: Quote glob patterns to let gitbatch handle expansion, especially on platforms where your shell might already expand globs.

• CLI built with Cobra for commands and flags.
• Uses doublestar for recursive glob support.

• Review output before committing/pushing.
• Use --yes only in trusted automation contexts.

• --dry-run to preview actions without modifying repositories.

Bug reports, PRs, and improvements are welcome. Please follow Go conventions, add tests for new behavior, and keep changes focused.