Only report updated files when some were updated - #333
Merged
Merged
Conversation
update-yaml --write prints its count unconditionally, so a run that changed nothing still prints "0 files were updated". Build systems that show a tool's output print that line for every target on every build, which buries the runs that did change something. Say nothing when the count is zero, which matches the dry run path below it: that already distinguishes "All files up to date" from a list of pending changes. Signed-off-by: Austin Schuh <austin.linux@gmail.com>
AustinSchuh
force-pushed
the
quiet-update-yaml
branch
from
September 18, 2026 04:28
894b632 to
cac1027
Compare
Member
|
update-yaml was originally intended to be ran by humans, so showing the action is useful. Stick this behind a |
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
Contributor
Author
|
That's an easy one, done! |
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
2 participants
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.
update-yaml --write prints its count unconditionally, so a run that changed nothing still prints "0 files were updated". Build systems that show a tool's output print that line for every target on every build, which buries the runs that did change something.