ingit 0.4.2

git repository collection management tool

Tool for managing a large collection of repositories in git. If you have 100 git-versioned projects, keeping tabs on everything can be quite troublesome.

That’s where ingit comes in. It mimics selected git commands, however you can perform the same action on a group of repositories instead of just one.

Additionally, it has an interactive mode in which you can go over your repositories and quickly perform typical suggested actions in each individual repository based on its current status.

overview

basic usage

For general help, see:

ingit -h

For command-specific help, see:

ingit command -h

Commands are of two kinds in general:

• git-like commands, which work similar to their git versions;

• ingit-only commands, which you won’t find in git.

Currently available ingit-only commands are:

ingit summary
ingit register

Currently available git-like commands are:

ingit clone
ingit init
ingit fetch
ingit checkout
ingit merge
ingit push
ingit gc
ingit status

configuration

Ingit workes based on configuration in 2 JSON files:

• runtime configuration

• repositories configuraion

If either of the files doesn’t exist, detaults will be generated.

The default paths to the files can be overriden via --config and --repos command-line options.

runtime configuraion

Most importantly, stores repositories root directory – it’s a directory which ingit assumes to contain git-versioned projects.

Example:

{
  "description": "ingit runtime configuration file",
  "ingit-version": "0.3.0",
  "machines": [
    {
      "name": "desktop",
      "repos_path": "~/Projects"
    },
    {
      "interactive": false,
      "names": ["server", "server.domain.com"],
      "repos_path": "$HOME/Projects"
    }
  ]
}

repositories configuraion

It’s a file that lists all registered projects.

Example:

{
  "description": "ingit repositories configuration file",
  "ingit-version": "0.3.0",
  "repos": [
    {
      "name": "ingit",
      "remotes": {
        "github": "[e-mail]:mbdevpl/ingit.git"
      },
      "tags": [
        "active",
        "git",
        "github",
        "my",
        "python"
      ]
    },
    {
      "name": "pylint",
      "remotes": {
        "github": "[e-mail]:mbdevpl/pylint.git",
        "source": "https://github.com/PyCQA/pylint"
      },
      "tags": [
        "external",
        "github",
        "python"
      ]
    }
  ]
}

command details

Below, details of each command are described.

ingit summary

Show summary of registered repositories and status of configured repository root.

First of all, print a list of registered repositories. By default, all registered repositories are listed, but, as in case of most commands, the results can be filtered via a predicate or regex.

Independently, print a list of all unregistered repositories and all not versioned paths present in the configured repositories root.

ingit register

Start tracking a repository in ingit.

ingit register [--tags TAG ...] [PATH]

The initial configuration is set according to basic repository information: its root directory name becomes “name”, its absolute path becomes “path”, and its currently configured remotes become “remotes”. You can edit the configuration manually afterwards.

Use PATH to provide the path to root directory of repository.

Use --tags to provide tags for this repository, they will be added to the initial configuration.

ingit status

Perform git status, as well as other diagnostic git commands.

Execute:

• git status --short to inform about any uncommited changes,

• git log tracking_branch..branch to inform about commits that are not yet pushed to the remote,

• git log branch..tracking_branch to inform about commits that are not yet merged from the remote.

Additionally, compare registered remotes with actual remotes to make sure that ingit configuration is in sync with the repository metadata.

other commands

TODO.

requirements

Python version >= 3.5.

Python libraries as specified in requirements.txt.

Building and running tests additionally requires packages listed in test_requirements.txt.

Tested on Linux, OS X and Windows.