We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
woodpecker-cli
cli
The latest update (v0.15.9) has updated the dependencies, and it looks like this might have changed a default value in the logging infrastructure.
When simply running woodpecker-cli, one can read the following message:
9:08PM ??? github.com/woodpecker-ci/woodpecker/cli/common/zerologger.go:20 > LogLevel = trace
N/A, this is purely a CLI thing.
This was noticed when bumping the version in nixpkgs: NixOS/nixpkgs#232073.
next
The text was updated successfully, but these errors were encountered:
The issue is still present in v0.15.10.
Sorry, something went wrong.
Do not print log level on CLI (#2638)
d5e68ef
if it's not in debug log level closes #1764
Successfully merging a pull request may close this issue.
Component
cli
Describe the bug
The latest update (v0.15.9) has updated the dependencies, and it looks like this might have changed a default value in the logging infrastructure.
When simply running
woodpecker-cli
, one can read the following message:System Info
Additional context
This was noticed when bumping the version in nixpkgs: NixOS/nixpkgs#232073.
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: