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
Add "human-readable-output" to the output of this action, similar to the standard output.
This will make it easier to see the results of the arduino-lint execution in the GitHub workflow summary.
Currently, the only way is to use "report-file" to output the execution results in json format
However, these are not in human readable format, so the results cannot be easily checked.
Also, although it is possible to check the standard output from the workflow logs to see the execution results in text format, this method requires time and effort to find the execution results in the workflow logs.
Using arduino-lint-action is good to notice errors immediately.
However, I use "report-file" to output the results in json format, but rarely actually check the json contents.
I would like to be able to easily see the cause of errors and warnings.
Describe the request
Add "human-readable-output" to the output of this action, similar to the standard output.
This will make it easier to see the results of the arduino-lint execution in the GitHub workflow summary.
As shown below (this is just an image I created)
Describe the current behavior
Currently, the only way is to use "report-file" to output the execution results in json format
However, these are not in human readable format, so the results cannot be easily checked.
Also, although it is possible to check the standard output from the workflow logs to see the execution results in text format, this method requires time and effort to find the execution results in the workflow logs.
'arduino/arduino-lint-action' version
1.0.2
Additional context
Here is the workflow I actually use "arduino/arduino-lint-action".
https://github.com/teruyamato0731/Chassis/actions/runs/7125200953
Using arduino-lint-action is good to notice errors immediately.
However, I use "report-file" to output the results in json format, but rarely actually check the json contents.
I would like to be able to easily see the cause of errors and warnings.
Issue checklist
The text was updated successfully, but these errors were encountered: