-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Rename use of --format
in ruff rule
to --output-format
#7990
Labels
cli
Related to the command-line interface
Comments
I got bitten by this when upgrading ruff as well. |
Yes... This broke my Github Action that uses ruff. I guessed something like this could be the reason, but it wasn't obvious to me from the ruff documentation that |
akx
added a commit
to akx/ruff
that referenced
this issue
Oct 25, 2023
…tion warnings Warnings borrowed from astral-sh#7514 Fixes astral-sh#7990
akx
added a commit
to akx/ruff
that referenced
this issue
Oct 25, 2023
…tion warnings Warnings borrowed from astral-sh#7514 Fixes astral-sh#7990
akx
added a commit
to akx/ruff
that referenced
this issue
Oct 26, 2023
…tion warnings Warnings borrowed from astral-sh#7514 Fixes astral-sh#7990
charliermarsh
pushed a commit
that referenced
this issue
Oct 28, 2023
…tion warnings (#8203) ## Summary Since `--format` was changed to `--output-format` for `check`, it feels like it makes sense for the same to work for the auxiliary commands. This * adds the same deprecation warning that used to be a thing in #7514 (and un-became a thing in #7984) Fixes #7990. ## Test Plan * `cargo run --bin=ruff -- rule --all --output-format=json` works * `cargo run --bin=ruff -- rule --format=json` works with warnings
justalemon
added a commit
to justalemon/5desc
that referenced
this issue
Dec 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As with #7354, we should probably rename
ruff rule --format ...
toruff rule --output-format ...
for clarity.The old option should be deprecated then removed later.
The text was updated successfully, but these errors were encountered: