2.1.0 (2023-08-28)
-
Added support for executing commands in the root repository. Closes #160. (commit)
Add the
$rootRepository
option to themrgit.json
configuration file to enable this feature. Its value should be a repository GitHub identifier (the same as defining thedependencies
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
.
2.0.3 (2023-06-05)
Internal changes only (updated dependencies, documentation, etc.).
2.0.2 (2023-06-02)
- The
status
andsync
commands will no longer fail when a repository has no tag. Closes #157. (commit)
2.0.1 (2022-12-07)
- Added the missing "scripts/postinstall.js" file to the published package. (commit)
2.0.0 (2022-12-07)
- A minimal version of
Node.js
has been increased to14
and fornpm
to5.7.1
.
- Fixed message displayed by the
status
command when using a specific commit defined in the config file. (commit)
- Upgraded dependencies and changed minimal versions for Node (
>=14.0.0
) and npm (>=5.7.1
). (commit, commit)
1.0.0 (2019-07-23)
- Repositories, where an executed command failed, will be printed out at the end of the mgit log. Closes #104. (2d1450c)
- mgit2 was renamed to mrgit.
0.11.1 (2019-07-16)
Internal changes only (updated dependencies, documentation, etc.).
0.11.0 (2019-07-15)
-
Allows cloning packages using the
file://
protocol. Closes #101. (d0aa893)Thanks to @neumann-d!
-
Introduced the
overrideDirectoryNames
option inmgit.json
. Closes #98.
- Number of unmerged files will be shown as "modified" in the table while execution the status command. Closes #107. (5481260)
0.10.1 (2019-01-14)
0.10.0 (2019-01-11)
-
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 formgit exec 'git commit -a'
)fetch
- allows fetching changes in all cloned repositories (a shorthand formgit exec 'git fetch'
)pull
- allows pulling changes in all cloned repositories and cloning missing ones (it does not check out to specified branch inmgit.json
file)push
- allows pushing changes in all cloned repositories (a shorthand formgit 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 tosync
. -
The
save-hashes
command was renamed tosave
. It accepts two options:--branch
or--hash
(which is default one). If specified--branch
, name of current branches will be saved inmgit.json
. -
Removed command
bootstrap
. Use thesync
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 inmgit.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. Callingmgit 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
.
-
- Removed the
bootstrap
command. Thesync
command should be used instead for initializing the repositories. - Renamed
update
command tosync
. - Renamed
save-hashes
command tosave
. It supports two parameters:--branch
and--hash
which the second one is set as default.
mgit checkout branch
will check out the repository on#branch
.[branch]
argument is optional. If it isn't specified, branch name will be taken frommgit.json
.
0.9.1 (2018-12-05)
- Simplified a check for "remote end hung up" error during the
bootstrap
command. Closes #92. (ed2291c)
0.9.0 (2018-11-22)
- The
mgit bootstrap
andmgit update
commands will try pulling changes twice in case of a network hang-up. Closes #87. (47e6840)
0.8.1 (2018-11-19)
0.8.0 (2018-05-04)
- Introduced a smarter
cwd
resolver which scans directory tree up in order to find themgit.json
file. If the file won't be found, an exception will be thrown. Closes #1. (751c10f)
0.7.5 (2018-05-04)
0.7.4 (2018-02-06)
Internal changes only (updated dependencies, documentation, etc.).
0.7.3 (2018-02-06)
- Not staged, deleted files were not shown as modified during mgit status command. Closes #58. (52ee784)
- The
status
command will now sort packages alphabetically. Closes #60. (56a31ce)
0.7.2 (2017-08-17)
Internal changes only (updated dependencies, documentation, etc.).
0.7.1 (2017-08-17)
-
Improved UI of the statuses table. Closes #55. (35349d0)
- If current branch is other than specified in
mgit.json
– the branch will be prefixed with!
, - If current branch is other than
master
– the whole row will be highlighted (in pink).
- If current branch is other than specified in
0.7.0 (2017-08-16)
-
Introduced new commands and fixed bugs related to incorrectly displayed errors. Closes #2. Closes #45. Closes #49. Closes #52. (c66c11a)
- New commands:
- Bug fixes:
- known errors should not be logged as crashes (see #45).
0.6.0 (2017-07-31)
- Introduced
--ignore
and--scope
options which allow executing the commands on a subset of packages. Closes #50. (061e32d)
0.5.2 (2017-07-04)
- Fixed various minor issues with the commands. Introduced missing tests. Closes #31. Closes #41. Closes #3. Closes #43. (5751eb7)
0.5.1 (2017-02-01)
- Empty package was published due to incorrect
files
configuration in `package.json. Fixes #37. (d6fc7c0)