astral-sh / astral-sh/ruff

Wrong configuration file indicated by ruff in verbose mode

Open
#18,643 1 comment 0 reactions 0 assignees View on GitHub
configuration
Dominant language
Rust
Stars
49.7k
Forks
2.4k
Avg merge
2d 1h
Merged PRs (30d)
458

Description

### Summary

If for example I have a pyproject.toml at repository root, and a ruff.toml inside debug/ subdirectory, then the settings of ruff.toml are the ones properly used for the launch, however the output improperly reports pyproject.toml as the configuration file (which is false).

```
❯ ruff check debug/ -v
[2025-06-12][12:17:55][ruff::resolve][DEBUG] Using configuration file (via parent) at: /[redacted]/pyproject.toml
[2025-06-12][12:17:55][ruff_workspace::pyproject][DEBUG] No `target-version` found in `ruff.toml`
```

I haven't tested all the cases, but I guess each hierarchical configuration file activated during the processing, should be indicated as so, in the program output (with verbose mode on).

### Version

0.11.13

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `ruff check debug/ -v` with `pyproject.toml` at the repository root and `ruff.toml` in `debug/`, then trace the configuration resolution and verbose logging. Done means verbose output identifies the hierarchical configuration file whose settings are actually used, including the `ruff.toml` case.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.