-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No verbosity at all for succesful checks #72
Comments
Came here to report this same issue, but with emphasis on the output for failed checks. The command line output is informative, showing exactly which imports are problematic. |
Agree. The docs say that the default option is equivalent to `isort . --check-only --diff' but I don't find that to be the case. @niemiaszek your links don't work for me. Maybe add extract of output here? I think I will add a new issue for my specific case, as it's not necessarily the same as yours. [Edit: done: #90 ] |
You're right, these links stopped working, as Github Actions runs have expiration date. Sorry for that, but it's been 1.5 year and I hoped to resolve this issue a bit faster. This Action seems abandoned. I stopped using this action so I won't be able to help. Last time I used isort in actions was with CLI. Currently I fully use Ruff for formatting and linting, with import sorting option (replacement for black and isort, with small differences). Looks like they're getting official Action support soon, where now you could use CLI with great success. |
Thanks @niemiaszek, no problem. I have moved to |
I tried to setup linting workflow using this action and it obviously works as intended, but it lacks any verbosity, even with --verbose option.
I'd expect successful workflow to output something similar to black formatter action, but there is none. Such example can be seen in this succesful check of mine. Verbosity for failed check exists, but I'd say it's also unsatisfying. Example in this failed check of mine.
Output of checks drastically differs from the one directly ran from isort cli.
The text was updated successfully, but these errors were encountered: