glab(1)

🌟 NAME 🌟

okay bestie, welcome to the glab(1) manual page πŸ’– β€” this one is all about glab-repo-publish-catalog, and its whole vibe is: [EXPERIMENTAL] Publishes CI/CD components to the catalog. periodt.


πŸ¦‹ SYNOPSIS πŸ¦‹

glab repo publish catalog  [flags]

✨ DESCRIPTION ✨

[EXPERIMENTAL] β€” yes, it's giving experimental, so keep that in mind πŸ’…. This command publishes CI/CD components in the project to the CI/CD catalog using the provided tag name.

Before it can slay, you need the feature flag ci_release_cli_catalog_publish_option to be enabled for this project in your GitLab instance. And it requires the same user as the release author β€” no cap, that part matters. 🫢

Here's the rundown, bestie:

  • It retrieves components from the current repository by searching for yml files within the "templates" directory and its subdirectories.
  • It fails if the feature flag ci_release_cli_catalog_publish_option is not enabled for this project in your GitLab instance. πŸ’€

Components can be defined in these iconic ways:

  • In single files ending in .yml for each component, like templates/secret-detection.yml.
  • In subdirectories containing template.yml files as entry points, for components that bundle together multiple related files. For example, templates/secret-detection/template.yml.

πŸŽ€ OPTIONS INHERITED FROM PARENT COMMANDS πŸŽ€

  • -h, --help[=false] β€” Show help for this command. lowkey iconic, highkey useful 🫢

🌈 EXAMPLE 🌈

run it like this, bestie ✨

glab repo publish catalog v1.2.3

πŸ”₯ SEE ALSO πŸ”₯


Auto generated by spf13/cobra πŸŽ€, dated Nov 2026, and living in the glab(1) manual β€” mwah, bye bestie πŸ’…βœ¨

πŸ“¦ where this page comes from