Skip to content

feat!: write text output to stdout#51

Merged
benner merged 1 commit into
mainfrom
feat/text-output-to-stdout
Apr 26, 2026
Merged

feat!: write text output to stdout#51
benner merged 1 commit into
mainfrom
feat/text-output-to-stdout

Conversation

@benner
Copy link
Copy Markdown
Owner

@benner benner commented Apr 26, 2026

Linters conventionally write results to stdout so users can pipe and
redirect them naturally. Writing to stderr made grep, redirection, and
piping all fail silently.

Switch _report_text and the range commit header from sys.stderr.write to
print (stdout). The "no commits in range" diagnostic remains on stderr
as it is an error condition, not result output.

Suppress T201 globally in ruff.toml since print is the intended output
mechanism for this CLI tool.

BREAKING CHANGE: text output now goes to stdout instead of stderr.

Linters conventionally write results to stdout so users can pipe and
redirect them naturally. Writing to stderr made grep, redirection, and
piping all fail silently.

Switch _report_text and the range commit header from sys.stderr.write to
print (stdout). The "no commits in range" diagnostic remains on stderr
as it is an error condition, not result output.

Suppress T201 globally in ruff.toml since print is the intended output
mechanism for this CLI tool.

BREAKING CHANGE: text output now goes to stdout instead of stderr.

Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
@benner benner marked this pull request as ready for review April 26, 2026 02:49
@benner benner merged commit 93007c1 into main Apr 26, 2026
4 checks passed
@benner benner deleted the feat/text-output-to-stdout branch April 26, 2026 02:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant