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
ymlfiles within the"templates"directory and its subdirectories. - It fails if the feature flag
ci_release_cli_catalog_publish_optionis not enabled for this project in your GitLab instance. π
Components can be defined in these iconic ways:
- In single files ending in
.ymlfor each component, liketemplates/secret-detection.yml. - In subdirectories containing
template.ymlfiles 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
- arch rolling: glab 1.128.0-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms