Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
ruff.toml
by nesting linter-specific configs under[lint]
(and related); though it would work (or, actually, works) the way it currently is, the proposed one could be a preferable/more future-proof option in sight of the upcoming deprecation of top-level lint settings discussed in[tool.ruff.lint]
usage in docs is inconsistent astral-sh/ruff#8449 or Deprecate top-level lint options astral-sh/ruff#7651fixable = ["ALL"]
is the default already as per https://docs.astral.sh/ruff/settings/#fixable. In my understanding,fixable
should be rather used to specify those rules - among the ones to be checked - that one wants to autofix as well (provided that an autofix is available and not unsafe)ignore
listcookiecutter
directoryPS: I'm not sure I correctly followed the contributing guidelines. The generated
testone
project didn't seem to embed the changes I committed before generating it; anyway, such configuration works on my side and should be backed by Ruff's docs as well