glab(1)

πŸ’… glab(1) β€” okay bestie, this is the glab config set page

Hi hi! So this is a page from the glab manual (that's the GitLab CLI, iykyk), and specifically it's all about the glab config set command. Buckle up, it's short but it's mighty ✨


🌸 NAME

glab-config-set β€” updates configuration with the value of a given key. That's literally the whole job, and it does it slayfully πŸ’…


πŸŽ€ SYNOPSIS

glab config set   [flags]

✨ DESCRIPTION

Okay so here's the tea 🍡 β€” use glab config set --global to write to the global configuration. And if you specify the --host flag, that also saves to the global configuration file.

And listen, this part matters: keys that glab manages for itself are always written to the global configuration, even if you don't pass --global. No cap β€” glab keeps its own stuff in the global file, periodt.


πŸ¦‹ OPTIONS

  • -g, --global[=false] β€” write to the global ~/.config/glab-cli/config.yml file instead of the repository's .git/glab-cli/config.yml file 🫢
  • --host="" β€” set a per-host setting. That's it, that's the vibe πŸ‘‘

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS

  • -h, --help[=false] β€” show help for this command. Iconic, helpful, always there for you πŸ₯Ή

🌈 EXAMPLE

Okay bestie, examples are the main character energy of any manpage, so here you go β€” exactly as written:

glab config set editor vim
glab config set token xxxxx --host gitlab.com
glab config set check_update false --global

Look at those three lines just existing and being useful. Ate, honestly. πŸ”₯


πŸ‘‘ SEE ALSO

  • glab-config(1) β€” go check out the parent command, it's giving family reunion πŸŽ€

πŸ’– little reminder: --global goes to ~/.config/glab-cli/config.yml, no --global goes to .git/glab-cli/config.yml, and --host always lands in the global one. Also glab's own keys are always global. Simple! Gorgeous! Slay! ✨

Auto generated by spf13/cobra, dated Nov 2026, and that's the whole manual page from the glab(1) set β€” mwah, bye bestie! πŸ’…πŸŒΈπŸ’–

πŸ“¦ where this page comes from