You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, executeProcess doesn't print stdout and stderr, but only returns the texts to the caller. If there is non-zero exit code and ignoreExitCode: true isn't set, then error is thrown with the stderr text in its message. Otherwise it is entirely up to the caller to print the process logs.
We could add a flag to toggle if process logs are printed, which would be less boilerplate than setting a custom observer object.
The question if logs should be printed by default or not. These logs would help with debugging, but could also be excessive in some cases.
If logs should not be printed by default, then we can add a verbose flag.
Context: #839 (comment)
Currently,
executeProcess
doesn't printstdout
andstderr
, but only returns the texts to the caller. If there is non-zero exit code andignoreExitCode: true
isn't set, then error is thrown with the stderr text in its message. Otherwise it is entirely up to the caller to print the process logs.We could add a flag to toggle if process logs are printed, which would be less boilerplate than setting a custom
observer
object.The question if logs should be printed by default or not. These logs would help with debugging, but could also be excessive in some cases.
verbose
flag.silent
flag (similarly to@actions/exec
.executeProcess
'ssilent
flag with the CLI's--verbose
option (silent: !verbose
).Acceptance critera
executeProcess
in the codebase and decide ifverbose
orsilent
would be more appropriate (do we usually want to print logs or not?)The text was updated successfully, but these errors were encountered: