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
After several experiments, isort action is lacking any verbosity for successful checks, even with --verbose option. Including --verbose option is still less verbose than black formatter action without --verbose option. Verbosity for failed checks is also minimal - just stating that a file is not formated with isort.
Verbosity might be good for some contributors. Especially beginners would want to be assured from github web that their code is passing linting check or have more information on why it is failing.
One way to solve this problem is setting up custom job directly running isort cli, which gives verbose output. Another way is checking out with python-isort action maintainers on this topic.
After several experiments, isort action is lacking any verbosity for successful checks, even with --verbose option. Including --verbose option is still less verbose than black formatter action without --verbose option. Verbosity for failed checks is also minimal - just stating that a file is not formated with isort.
Verbosity might be good for some contributors. Especially beginners would want to be assured from github web that their code is passing linting check or have more information on why it is failing.
One way to solve this problem is setting up custom job directly running isort cli, which gives verbose output. Another way is checking out with python-isort action maintainers on this topic.
Issue has been created in isort-actions repository
The text was updated successfully, but these errors were encountered: