-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include killed
boolean in command result
#250
Conversation
Any chance we can get this PR considered? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey! Can we also get some test for this, please?
As far as I can tell there are no existing tests that test the exit condition of multiple commands in the |
OK, I figured it out. Been so long since I did this I had forgotten the structure of the project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the side fixes!
Do I have to do anything to merge this? I assume you'll merge it at some point. |
Any idea when this will be released? |
Heya. Just released it in v6.2.0. |
brilliant, thanks |
The exit code of each command is already included in the result but the usefulness of this is limited if concurrently is run with
killOthers
. When parsing the result you do not know if a non-0 exit code is because the command failed or if it was killed by concurrently.Adding this option allows you to print a message at the end identifying exactly which commands caused the initial failure.