New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: make nugget quiet by default #16147
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of removing the option to set quiet, I'd prefer that quiet could be turned off or on from a command line argument. I'm fine if it defaults to quiet but if someone is manually finishing a release, they might want the more verbose output.
lint failure fixed by: #16153. |
No Release Notes |
/trop run backport-to 4-0-x,3-1-x,3-0-x |
The backport process for this PR has been manually initiated, |
The backport process for this PR has been manually initiated, |
The backport process for this PR has been manually initiated, |
I have automatically backported this PR to "4-0-x", please check out #16154 |
I was unable to backport this PR to "3-1-x" cleanly; |
I was unable to backport this PR to "3-0-x" cleanly; |
Description of Change
nugget
's output is useful when the release script is being run by humans, but now that Sudowoodo handles releases its output clogs Papertrail and makes it harder to spot more prescient errors. This PR this makesnugget
quiet unless--verboseNugget
is passed./cc @jkleinsc
Checklist
npm test
passesRelease Notes
Notes: no-notes