Vince Chan e2109c1353 Improve debug printing for resolving origin of config settings (#8729) ...

## Summary

When running ruff in verbose mode with `-v`, the first debug logs show
where the config settings are taken from. For example:
```
❯ ruff check ./some_file.py -v
[2023-11-17][00:16:25][ruff_cli::resolve][DEBUG] Using pyproject.toml (parent) at /Users/vince/demo/ruff.toml
```

This threw me off for a second because I knew I had no python project
there, and therefore no `pyproject.toml` file. Then I realised it was
actually reading a `ruff.toml` file (obvious when you read the whole
print I suppose) and that the pyproject.toml is a hardcoded string in
the debug log.

I think it would be nice to tweak the wording slightly so it is clear
that the settings don't neccessarily have to come from a
`pyproject.toml` file.

2023-11-17 01:10:36 +00:00

..

resources/test/fixtures

Preserve trailing semicolon for Notebooks (#8590)

2023-11-10 21:53:35 +05:30

src

Improve debug printing for resolving origin of config settings (#8729)

2023-11-17 01:10:36 +00:00

tests

Update to Rust 1.74 and use new clippy lints table (#8722)

2023-11-16 18:12:46 -05:00

build.rs

Add ruff version with long version display (#8034)

2023-10-20 14:07:41 -05:00

Cargo.toml

Update to Rust 1.74 and use new clippy lints table (#8722)

2023-11-16 18:12:46 -05:00