-
Notifications
You must be signed in to change notification settings - Fork 44
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
Buildkite Package Registries command help wording fixes. #440
Conversation
…current product name, make packages sound more like files, to make them more applicable to other package ecosystems, and correct name reference to slug.
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.
🚀
Use: "push registry-name {path/to/file | --stdin-file-name filename -}", | ||
Short: "Push a new package to Buildkite Packages", | ||
Use: "push registry-slug {path/to/file | --stdin-file-name filename -}", |
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.
An important change, considering slugs and names are distinctly different.
Push a new package to Buildkite Packages. The package can be passed as a path to a file in the second positional argument, | ||
or via stdin. If passed via stdin, the filename must be provided with the --stdin-file-name flag, as Buildkite | ||
Packages requires a filename for the package.`), | ||
Push a new package to a Buildkite registry. The package can be passed as a path to a file in the second positional argument, |
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.
A "Buildkite registry" is more accurate/specific than the former product name "Buildkite Packages", and less cumbersome than referring to this type of registry as a "Buildkite Package Registries registry".
Updating wording of Buildkite Package Registries commands to reflect:
Not all package ecosystems refer to their files as packages - e.g. 'modules' for Terraform, 'charts' for Helm, 'images' for 'container (Docker)', etc.