Getting Started

Install gip and run your first bulk git operation

CONTENTS

Installation

Download the latest binary from GitHub Releases and place it on your $PATH.

# Linux / macOS — make it executable
chmod +x gip
sudo mv gip /usr/local/bin/gip

# Verify
gip --version

Or build from source (requires Go 1.21+):

git clone https://github.com/enr/gip
cd gip
./.sdlc/build
# binary is placed in ./bin/gip

Create a config file

Create ~/.gip (YAML or JSON) listing the repositories you want to manage:

- name: frontend
  repository: "https://github.com/org/frontend.git"
  local_path: ~/projects/frontend
  tags: [work, js]

- name: dotfiles
  repository: "git@github.com:user/dotfiles.git"
  local_path: ~/dotfiles
  tags: [personal]

- name: legacy
  repository: "https://github.com/org/legacy.git"
  local_path: ~/projects/legacy
  pull_policy: never

See Configuration for all available fields.

First commands

Check the status of all repos:

gip status

Pull the latest changes:

gip pull

See which branch each repo is on:

gip branch

List all registered projects:

gip list

Get a richer overview

Add --extended to branch or list for a dashboard view with sync status, dirty indicators, and last commit info:

gip branch --extended
gip list --extended

NAME        BRANCH    STATUS    DIRTY  COMMIT                    DATE        PATH
frontend    main      synced    —      chore: bump deps          3 days ago  ~/projects/frontend
backend     dev       ↑2        +*     feat: add auth endpoint   2 hours ago ~/projects/backend
dotfiles    main      ↓1        —      docs: update README       1 week ago  ~/dotfiles

STATUS colour: green = synced · magenta = ahead · yellow = behind · red = diverged · white = no remote
DIRTY symbols: + staged · * unstaged · ? untracked · $ stash

Focus on repos that need attention

Use --dirty or --behind to limit any command to repos that match:

# only repos with uncommitted changes
gip status --dirty
gip branch --dirty --extended

# only repos behind their upstream (run fetch first)
gip fetch && gip pull --behind

Filter by tag

Run any command against a tagged subset:

# only repos tagged "work"
gip status --tag work

# OR logic — repos tagged "js" or "personal"
gip pull --tag js,personal

Scan existing repos

If you already have repos cloned and want to generate a config file from them:

gip init ~/projects
# writes to ~/.gip by default

← Configuration