Skip to content
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

Merged
merged 2 commits into from
Feb 13, 2025

Conversation

gilesgas
Copy link
Contributor

@gilesgas gilesgas commented Feb 13, 2025

Updating wording of Buildkite Package Registries commands to reflect:

  • current product name,
  • make packages sound more like files, to make them more applicable to other package ecosystems, and
  • correct name reference to slug.

Not all package ecosystems refer to their files as packages - e.g. 'modules' for Terraform, 'charts' for Helm, 'images' for 'container (Docker)', etc.

…current product name, make packages sound more like files, to make them more applicable to other package ecosystems, and correct name reference to slug.
Copy link
Contributor

@lizrabuya lizrabuya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@gilesgas gilesgas requested a review from moskyb February 13, 2025 01:22
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 -}",
Copy link
Contributor Author

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,
Copy link
Contributor Author

@gilesgas gilesgas Feb 13, 2025

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".

@gilesgas gilesgas merged commit 6ee6d7d into main Feb 13, 2025
1 check passed
@gilesgas gilesgas deleted the fix-internal-help-for-package-push-command branch February 13, 2025 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants