fix(pr): write rate limit and API error messages to stderr#3
Merged
vdemeester merged 2 commits intomainfrom Jan 30, 2026
Merged
fix(pr): write rate limit and API error messages to stderr#3vdemeester merged 2 commits intomainfrom
vdemeester merged 2 commits intomainfrom
Conversation
Info messages are metadata about the process, not actual output. Writing them to stderr allows piping stdout to other tools like lazypr: nixpkgs-pr-watch -o urls | xargs lazypr Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
These messages are operational logs, not program output. Writing them to stderr allows piping stdout to other tools. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Operational logs should go to stderr, not stdout.