Refining logging level for OS command calls #1147
Open
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.
Dear maintainers,
I have been utilizing this library for integration within my environment (private fork sbt-frontend). I came across a minor yet irksome issue related to the logging of operating system commands. When the workflow runs seamlessly, the logs are not of particular interest to me. However, in the event of an error, I would greatly appreciate the ability to access detailed information regarding the problem.
Currently, all logs are written at the
INFO
level which means I have to sift through a significant amount of "noise" in the logs when all is well, just to ensure I will have available error messages in case of issues arising.I have submitted a pull request addressing this specific issue and would appreciate if you could kindly review it. Thank you in advance for your time and consideration.