glab(1)

πŸ’– NAME πŸ’–

glab-variable β€” bestie, this is your whole toolkit for managing variables on a GitLab project or a group. Yes, both. We contain multitudes. ✨

Also hi, you're reading the glab(1) manual family β€” welcome to the group chat 🫢


🌸 SYNOPSIS 🌸

glab variable [flags]

That's it. That's the whole vibe. Run it, then pick a subcommand like the main character you are πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so listen: variables are literally where your config and your secrets live for CI/CD pipelines. Configuration? Secrets? All of it. Stored as variables. Iconic behaviour, no cap πŸ”₯

Now here's the part you gotta remember, bestie β€” by default every single subcommand acts on the current project. That's the default. That's the baseline. But if you wanna be managing a group's variables instead? Just pass --group and boom, you're in group mode. Two vibes, one command, we love to see it πŸ‘‘


✨ OPTIONS ✨

  • -R, --repo="" β€” picks a different repository for you. Default is empty string "", obviously. You can hand it OWNER/REPO or GROUP/NAMESPACE/REPO, and if you're feeling extra the full URL or a Git URL is also accepted. Flexible queen πŸ’…

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

  • -h, --help[=false] β€” shows help for this command. Look at us, being all self-aware. Default is false, so it won't spam you unprompted πŸ™ˆ

🌈 SEE ALSO 🌈

The whole friend group, fr fr:


Lowkey a whole squad of subcommands waiting for you. Go read them too, iykyk πŸ’œ

Auto generated by spf13/cobra 🌸 dated Nov 2026 πŸ¦‹ and it's part of the glab(1) family β€” mwah, go slay your pipelines bestie πŸ’–βœ¨

πŸ“¦ where this page comes from