-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
woodpecker-cli misnamed in RPM and DEB releases #2112
Comments
That's the intended name for the binary. |
In that case, should I change the report to 'standardize woodpecker-cli binary name' or something like that? |
I think this is also intended to differentiate it from server and agent, but the binary itself should be called |
binary currently should be:
as it's handy for autocompletion in shell, I would argue ... but if the package name also should just be called that way I dont know ... |
I'll close this as there was no response and @6543 explained why it is called this way. |
The intended executable name is supposed to be `woodpecker`, not `woodpecker-cli`, as pointed out in [1]. [1]: woodpecker-ci/woodpecker#2112
Component
cli
Describe the bug
woodpecker-cli's RPM and DEB packages install a binary called 'woodpecker' as opposed to 'woodpecker-cli'. The binary appears to work, but this is confusing as the examples (and tarball releases) use the name 'woodpecker-cli'.
System Info
Additional context
Fedora:
Debian:
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: