-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
feat(core): improve run-command parallel logs #9006
feat(core): improve run-command parallel logs #9006
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/DaugAA4sRvt7CNWQoiz2B1ma5NBy [Deployment for de7bfdd canceled] |
1d1e5e2
to
fc5ddb9
Compare
It appends the executed command on the result line, so it is easier to distinguish from which command the log line is related to. This change only affects the log when `parallel` is `true`.
fc5ddb9
to
de7bfdd
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
It appends the executed command on the result line, so it is easier to distinguish from which command the log line is related to. Format is
[command] result line
.This change only affects the log when
parallel
istrue
.This allows to search for a specific command while debugging, making it easier to aggregate logs by commands when using external log tooling (like Google Log Explorer).
Here is an example of how it looks like: