for-each-repo: optionally keep going on an error
In https://github.com/microsoft/git/issues/623, it was reported that the regularly scheduled maintenance stops if one repo in the middle of the list was found to be missing. This is undesirable, and points out a gap in the design of `git for-each-repo`: We need a mode where that command does not stop on an error, but continues to try running the specified command with the other repositories. Imitating the `--keep-going` option of GNU make, this commit teaches `for-each-repo` the same trick: to continue with the operation on all the remaining repositories in case there was a problem with one repository, still setting the exit code to indicate an error occurred. Helped-by: Eric Sunshine <sunshine@sunshineco.com> Helped-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
3c2a3fdc38
commit
12c2ee5fbd
@ -42,6 +42,15 @@ These config values are loaded from system, global, and local Git config,
|
||||
as available. If `git for-each-repo` is run in a directory that is not a
|
||||
Git repository, then only the system and global config is used.
|
||||
|
||||
--keep-going::
|
||||
Continue with the remaining repositories if the command failed
|
||||
on a repository. The exit code will still indicate that the
|
||||
overall operation was not successful.
|
||||
+
|
||||
Note that the exact exit code of the failing command is not passed
|
||||
through as the exit code of the `for-each-repo` command: If the command
|
||||
failed in any of the specified repositories, the overall exit code will
|
||||
be 1.
|
||||
|
||||
SUBPROCESS BEHAVIOR
|
||||
-------------------
|
||||
|
Reference in New Issue
Block a user