v2.1.0

Features

• Added support for executing commands in the root repository. Closes #160. (commit)

  Add the $rootRepository option to the mrgit.json configuration file to enable this feature. Its value should be a repository GitHub identifier (the same as defining the dependencies values). You can also define the option within the preset feature.

  Below, you can find a list of supported commands that take into consideration the root repository if specified:

  • checkout
  • commit
  • diff
  • exec
  • fetch
  • pull
  • push
  • status
  • sync

  To disable executing a command in the root repository without modifying the configuration file, you can add the --skip-root modifier to mrgit. Example: mrgit status --skip-root.

v2.0.3

Internal changes only (updated dependencies, documentation, etc.).

v2.0.2

Bug fixes

• The status and sync commands will no longer fail when a repository has no tag. Closes #157. (commit)

v2.0.1

Bug fixes

• Added the missing "scripts/postinstall.js" file to the published package. (commit)

v2.0.0

BREAKING CHANGES

• A minimal version of Node.js has been increased to 14 and for npm to 5.7.1.

Features

• Added support for presets. Closes #151. (commit)
• Added support for tags. Closes #148. (commit)

Bug fixes

• Fixed message displayed by the status command when using a specific commit defined in the config file. (commit)

Other changes

• Upgraded dependencies and changed minimal versions for Node (>=14.0.0) and npm (>=5.7.1). (commit, commit)

v1.0.0

Features

• Repositories, where an executed command failed, will be printed out at the end of the mgit log. Closes #104. (2d1450c)

Other changes

• RIP mgit2 💀 Long live mrgit 🎉 Closes #85. (4a2a33f)

BREAKING CHANGES

• mgit2 was renamed to mrgit.

v0.11.1

Internal changes only (updated dependencies, documentation, etc.).

v0.11.0

Features

• Allows cloning packages using the file:// protocol. Closes #101. (d0aa893)

  Thanks to @neumann-d!

• Added support for base branches. Closes #103. (51eded0)

• Introduced the overrideDirectoryNames option in mgit.json. Closes #98.

Bug fixes

• Number of unmerged files will be shown as "modified" in the table while execution the status command. Closes #107. (5481260)

v0.10.1

Bug fixes

• The master repository package should not be loaded to packages dir. Closes #96. (7814c33)

v0.10.0

Features

• Introduced a set of new commands which should help developers in daily tasks. Closes #73. (2097c16)

  • New commands:

    • commit - allows committing all changes files that are tracked by Git (a shorthand for mgit exec 'git commit -a')
    • fetch - allows fetching changes in all cloned repositories (a shorthand for mgit exec 'git fetch')
    • pull - allows pulling changes in all cloned repositories and cloning missing ones (it does not check out to specified branch in mgit.json file)
    • push - allows pushing changes in all cloned repositories (a shorthand for mgit exec 'git push')
    • close - allows mering specified branch into current one and removes the merged branch from the local and remote

  • The update command was renamed to sync.

  • The save-hashes command was renamed to save. It accepts two options: --branch or --hash (which is default one). If specified --branch, name of current branches will be saved in mgit.json.

  • Removed command bootstrap. Use the sync command instead. Sync command will scan the package directories and compare results with packages saved in configuration file. If there is something that is not defined in mgit.json, it will be printed out.

  • checkout command now allows checking out the project to specified branch: mgit checkout stable will check out all repositories to #stable branch. It can also create a new branch for repositories that contains changes in files tracked by git. Calling mgit checkout -- --branch develop will create the #develop branch in these repositories.

  • Improved the help screen of mgit and introduced a help screen for specified command, e.g.: mgit sync --help.

BREAKING CHANGES

• Removed the bootstrap command. The sync command should be used instead for initializing the repositories.
• Renamed update command to sync.
• Renamed save-hashes command to save. It supports two parameters: --branch and --hash which the second one is set as default.

NOTE

• mgit checkout branch will check out the repository on #branch. [branch] argument is optional. If it isn't specified, branch name will be taken from mgit.json.