Return failure code to the system when commands fail #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently mu will always return 0 to the system even when the git commands have failed.
While it is definitely good to always try the operations in all repositories (instead of stopping at the first error), always returning 0 to the system makes using 'mu' in scripts difficult, as we cannot easily be sure that the operations were successful.
In addition, this will now print (in red) the repositories where the operation has failed: a very common beginner mistake when using
mu
is to not notice that the command failed for one of the repositories, as it may end up at the top of the output.Here is a screenshot of
mu checkout foobar
where onlyben10
has that branch: