multi-gitter allows you to make changes in multiple repositories simultaneously. This is achieved by running a script or program in the context of multiple repositories. If any changes are made, a pull request is created that can be merged manually by the set reviewers, or automatically by multi-gitter when CI pipelines has completed successfully.

Are you a bash-guru or simply prefer your scripting in Node.js? It doesn't matter, since multi-gitter support any type of script or program. If you can script it to run in one place, you can run it in all your repositories with one command!

Some examples:

• Syncing a file (like a PR-template)
• Programmatic refactoring
• Updating a dependency
• Automatically fixing linting issues
• Search and replace
• Anything else you are able to script!

Demo

Example

Run with file

$ multi-gitter run ./my-script.sh -O my-org -m "Commit message" -B branch-name

Make sure the script has execution permissions before running it (chmod +x ./my-script.sh)

Run code through interpreter

If you are running an interpreted language or similar, it's important to specify the path as an absolute value (since the script will be run in the context of each repository). Using the $PWD variable helps with this.

$ multi-gitter run "python $PWD/run.py" -O my-org -m "Commit message" -B branch-name
$ multi-gitter run "node $PWD/script.js" -R repo1 -R repo2 -m "Commit message" -B branch-name
$ multi-gitter run "go run $PWD/main.go" -U my-user -m "Commit message" -B branch-name

Test before live run

You might want to test your changes before creating commits. The --dry-run provides an easy way to test without actually making any modifications. It works well with setting the log level to debug with --log-level=debug to also print the changes that would have been made.

$ multi-gitter run ./script.sh --dry-run --log-level=debug -O my-org -m "Commit message" -B branch-name

Install

Homebrew

If you are using Mac or Linux, Homebrew is an easy way of installing multi-gitter.

brew install lindell/multi-gitter/multi-gitter

Manual binary install

Find the binary for your operating system from the release page and download it.

Automatic binary install

To automatically install the latest version

curl -s https://raw.githubusercontent.com/lindell/multi-gitter/master/install.sh | sh

From source

You can also install from source with go get, this is not recommended for most cases.

go get github.com/lindell/multi-gitter

Token

To use multi-gitter, a token that is allowed to list repositories and create pull requests is needed. This token can either be set in the GITHUB_TOKEN, GITLAB_TOKEN, GITEA_TOKEN environment variable, or by using the --token flag.

GitHub

How to generate a GitHub personal access token. Make sure to give to repo permissions.

GitLab

How to generate a GitLab personal access token. Make sure to give to it the api permission.

Gitea

In Gitea, access tokens can be generated under Settings -> Applications -> Manage Access Tokens

Usage

• run Clones multiple repositories, run a script in that directory, and creates a PR with those changes.
• merge Merge pull requests.
• status Get the status of pull requests.
• close Close pull requests.
• print Clones multiple repositories, run a script in that directory, and prints the output of each run.

Usage of run

This command will clone down multiple repositories. For each of those repositories, the script will be run in the context of that repository. If the script finished with a zero exit code, and the script resulted in file changes, a pull request will be created with.

The environment variable REPOSITORY will be set to the name of the repository currently being executed by the script.

Usage:
  multi-gitter run [script path] [flags]

Flags:
      --author-email string     Email of the committer. If not set, the global git config setting will be used.
      --author-name string      Name of the committer. If not set, the global git config setting will be used.
      --base-branch string      The branch which the changes will be based on.
  -g, --base-url string         Base URL of the (v3) GitHub API, needs to be changed if GitHub enterprise is used. Or the url to a self-hosted GitLab instance.
  -B, --branch string           The name of the branch where changes are committed. (default "multi-gitter-branch")
  -m, --commit-message string   The commit message. Will default to title + body if none is set.
  -C, --concurrent int          The maximum number of concurrent runs (default 1)
  -d, --dry-run                 Run without pushing changes or creating pull requests
  -f, --fetch-depth int         Limit fetching to the specified number of commits. Set to 0 for no limit (default 1)
      --fork                    Fork the repository instead of creating a new branch on the same owner
      --fork-owner string       If set, make the fork to defined one. Default behavior is for the fork to be on the logged in user.
      --git-type string         The type of git implementation to use.
                                Available values:
                                  go: Uses go-git, a Go native implementation of git. This is compiled with the multi-gitter binary, and no extra dependencies are needed.
                                  cmd: Calls out to the git command. This requires git to be installed and available with by calling "git".
                                 (default "go")
  -G, --group strings           The name of a GitLab organization. All repositories in that group will be used.
      --include-subgroups       Include GitLab subgroups when using the --group flag.
      --log-file string         The file where all logs should be printed to. "-" means stdout (default "-")
      --log-format string       The formating of the logs. Available values: text, json, json-pretty (default "text")
  -L, --log-level string        The level of logging that should be made. Available values: trace, debug, info, error (default "info")
  -M, --max-reviewers int       If this value is set, reviewers will be randomized
  -O, --org strings             The name of a GitHub organization. All repositories in that organization will be used.
  -o, --output string           The file that the output of the script should be outputted to. "-" means stdout (default "-")
  -p, --platform string         The platform that is used. Available values: github, gitlab, gitea (default "github")
  -b, --pr-body string          The body of the commit message. Will default to everything but the first line of the commit message if none is set.
  -t, --pr-title string         The title of the PR. Will default to the first line of the commit message if none is set.
  -P, --project strings         The name, including owner of a GitLab project in the format "ownerName/repoName"
  -R, --repo strings            The name, including owner of a GitHub repository in the format "ownerName/repoName"
  -r, --reviewers strings       The username of the reviewers to be added on the pull request.
      --skip-pr                 Skip pull request and directly push to the branch
  -T, --token string            The GitHub/GitLab personal access token. Can also be set using the GITHUB_TOKEN/GITLAB_TOKEN environment variable.
  -U, --user strings            The name of a user. All repositories owned by that user will be used.

Usage of merge

Merge pull requests with a specified branch name in an organization and with specified conditions.

Usage:
  multi-gitter merge [flags]

Flags:
  -g, --base-url string      Base URL of the (v3) GitHub API, needs to be changed if GitHub enterprise is used. Or the url to a self-hosted GitLab instance.
  -B, --branch string        The name of the branch where changes are committed. (default "multi-gitter-branch")
  -G, --group strings        The name of a GitLab organization. All repositories in that group will be used.
      --include-subgroups    Include GitLab subgroups when using the --group flag.
      --log-file string      The file where all logs should be printed to. "-" means stdout (default "-")
      --log-format string    The formating of the logs. Available values: text, json, json-pretty (default "text")
  -L, --log-level string     The level of logging that should be made. Available values: trace, debug, info, error (default "info")
      --merge-type strings   The type of merge that should be done (GitHub). Multiple types can be used as backup strategies if the first one is not allowed. (default [merge,squash,rebase])
  -O, --org strings          The name of a GitHub organization. All repositories in that organization will be used.
  -p, --platform string      The platform that is used. Available values: github, gitlab, gitea (default "github")
  -P, --project strings      The name, including owner of a GitLab project in the format "ownerName/repoName"
  -R, --repo strings         The name, including owner of a GitHub repository in the format "ownerName/repoName"
  -T, --token string         The GitHub/GitLab personal access token. Can also be set using the GITHUB_TOKEN/GITLAB_TOKEN environment variable.
  -U, --user strings         The name of a user. All repositories owned by that user will be used.

Usage of status

Get the status of all pull requests with a specified branch name in an organization.

Usage:
  multi-gitter status [flags]

Flags:
  -g, --base-url string     Base URL of the (v3) GitHub API, needs to be changed if GitHub enterprise is used. Or the url to a self-hosted GitLab instance.
  -B, --branch string       The name of the branch where changes are committed. (default "multi-gitter-branch")
  -G, --group strings       The name of a GitLab organization. All repositories in that group will be used.
      --include-subgroups   Include GitLab subgroups when using the --group flag.
      --log-file string     The file where all logs should be printed to. "-" means stdout (default "-")
      --log-format string   The formating of the logs. Available values: text, json, json-pretty (default "text")
  -L, --log-level string    The level of logging that should be made. Available values: trace, debug, info, error (default "info")
  -O, --org strings         The name of a GitHub organization. All repositories in that organization will be used.
  -o, --output string       The file that the output of the script should be outputted to. "-" means stdout (default "-")
  -p, --platform string     The platform that is used. Available values: github, gitlab, gitea (default "github")
  -P, --project strings     The name, including owner of a GitLab project in the format "ownerName/repoName"
  -R, --repo strings        The name, including owner of a GitHub repository in the format "ownerName/repoName"
  -T, --token string        The GitHub/GitLab personal access token. Can also be set using the GITHUB_TOKEN/GITLAB_TOKEN environment variable.
  -U, --user strings        The name of a user. All repositories owned by that user will be used.

Usage of close

Close pull requests with a specified branch name in an organization and with specified conditions.

Usage:
  multi-gitter close [flags]

Flags:
  -g, --base-url string     Base URL of the (v3) GitHub API, needs to be changed if GitHub enterprise is used. Or the url to a self-hosted GitLab instance.
  -B, --branch string       The name of the branch where changes are committed. (default "multi-gitter-branch")
  -G, --group strings       The name of a GitLab organization. All repositories in that group will be used.
      --include-subgroups   Include GitLab subgroups when using the --group flag.
      --log-file string     The file where all logs should be printed to. "-" means stdout (default "-")
      --log-format string   The formating of the logs. Available values: text, json, json-pretty (default "text")
  -L, --log-level string    The level of logging that should be made. Available values: trace, debug, info, error (default "info")
  -O, --org strings         The name of a GitHub organization. All repositories in that organization will be used.
  -p, --platform string     The platform that is used. Available values: github, gitlab, gitea (default "github")
  -P, --project strings     The name, including owner of a GitLab project in the format "ownerName/repoName"
  -R, --repo strings        The name, including owner of a GitHub repository in the format "ownerName/repoName"
  -T, --token string        The GitHub/GitLab personal access token. Can also be set using the GITHUB_TOKEN/GITLAB_TOKEN environment variable.
  -U, --user strings        The name of a user. All repositories owned by that user will be used.

Usage of print

This command will clone down multiple repositories. For each of those repositories, the script will be run in the context of that repository. The output of each script run in each repo will be printed, by default to stdout and stderr, but it can be configured to files as well.

The environment variable REPOSITORY will be set to the name of the repository currently being executed by the script.

Usage:
  multi-gitter print [script path] [flags]

Flags:
  -g, --base-url string       Base URL of the (v3) GitHub API, needs to be changed if GitHub enterprise is used. Or the url to a self-hosted GitLab instance.
  -C, --concurrent int        The maximum number of concurrent runs (default 1)
  -E, --error-output string   The file that the output of the script should be outputted to. "-" means stderr (default "-")
  -f, --fetch-depth int       Limit fetching to the specified number of commits. Set to 0 for no limit (default 1)
      --git-type string       The type of git implementation to use.
                              Available values:
                                go: Uses go-git, a Go native implementation of git. This is compiled with the multi-gitter binary, and no extra dependencies are needed.
                                cmd: Calls out to the git command. This requires git to be installed and available with by calling "git".
                               (default "go")
  -G, --group strings         The name of a GitLab organization. All repositories in that group will be used.
      --include-subgroups     Include GitLab subgroups when using the --group flag.
      --log-file string       The file where all logs should be printed to. "-" means stdout
      --log-format string     The formating of the logs. Available values: text, json, json-pretty (default "text")
  -L, --log-level string      The level of logging that should be made. Available values: trace, debug, info, error (default "info")
  -O, --org strings           The name of a GitHub organization. All repositories in that organization will be used.
  -o, --output string         The file that the output of the script should be outputted to. "-" means stdout (default "-")
  -p, --platform string       The platform that is used. Available values: github, gitlab, gitea (default "github")
  -P, --project strings       The name, including owner of a GitLab project in the format "ownerName/repoName"
  -R, --repo strings          The name, including owner of a GitHub repository in the format "ownerName/repoName"
  -T, --token string          The GitHub/GitLab personal access token. Can also be set using the GITHUB_TOKEN/GITLAB_TOKEN environment variable.
  -U, --user strings          The name of a user. All repositories owned by that user will be used.

Example scripts

general

#!/bin/bash

REPLACE_FILE=~/test/pull_request_template.md # The file that should replace the file in the repo, must be an absolute path
FILE=.github/pull_request_template.md # Relative from any repos root

# Don't replace this file if it does not already exist in the repo
if [ ! -f "$FILE" ]; then
    exit 1
fi

cp $REPLACE_FILE $FILE

#!/bin/bash

# Assuming you are using gnu sed, if you are running this on a mac, please see https://stackoverflow.com/questions/4247068/sed-command-with-i-option-failing-on-mac-but-works-on-linux

find ./ -type f -exec sed -i -e 's/apple/orange/g' {} \;

go

#!/bin/bash

golangci-lint run ./... --fix

#!/bin/bash

### Change these values ###
MODULE=github.com/go-git/go-git/v5
VERSION=v5.1.0

# Check if the module already exist, abort if it does not
go list -m $MODULE &> /dev/null
status_code=$?
if [ $status_code -ne 0 ]; then
    echo "Module \"$MODULE\" does not exist"
    exit 1
fi

go get $MODULE@$VERSION

node

#!/bin/bash

### Change these values ###
PACKAGE=webpack
VERSION=4.43.0

if [ ! -f "package.json" ]; then
    echo "package.json does not exist"
    exit 1
fi

# Check if the package already exist (without having to install all packages first), abort if it does not
current_version=`jq ".dependencies[\"$PACKAGE\"]" package.json`
if [ "$current_version" == "null" ];
then
    echo "Package \"$PACKAGE\" does not exist"
    exit 2
fi

npm install --save $PACKAGE@$VERSION

const { readFile, writeFile } = require("fs").promises;

async function replace() {
  let data = await readFile("./README.md", "utf8");
  data = data.replace("apple", "orange");
  await writeFile("./README.md", data, "utf8");
}

replace();