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 a new --output=github option to format errors as Workflow commands, similar to --output=json added in #11396.
Pitch
For example, for this output in JSON format
$ mypy src --output=json{"file": "src/mylib/client.py", "line": 759, "column": 20, "message": "Argument 1 to \"export_responses\" of \"Client\" has incompatible type \"str\"; expected \"int\"", "hint": null, "code": "arg-type", "severity": "error"}
we'd get the following output in workflow command format
$ mypy src --output=json::error file=src/mylib/client.py,line=759,col=20::(`arg-type`) Argument 1 to "export_responses" of "Client" has incompatible type "str"
I'm not the person who opened the issue, but yes, I think this would support allowing annotations, similar to ruff check --output-format github or using pylint with the pylint-actions plugin.
I'm not the person who opened the issue, but yes, I think this would support allowing annotations, similar to ruff check --output-format github or using pylint with the pylint-actions plugin.
Feature
Add a new
--output=github
option to format errors as Workflow commands, similar to--output=json
added in #11396.Pitch
For example, for this output in JSON format
we'd get the following output in workflow command format
Related:
--output=json
CLI option #17611The text was updated successfully, but these errors were encountered: