glab(1)

πŸ“¦
version 1.128.0 Β· 2 versions
, in arch rolling

πŸŽ€ NAME πŸŽ€

glab-config-path β€” prints the location of the global configuration file. Welcome to the glab(1) manual, bestie; we’re about to find your config file’s address, no cap. πŸ’…

✨ SYNOPSIS ✨

glab config path [flags]

🌸 DESCRIPTION 🌸

Okay so this command prints where glab reads and writes its global configuration. The exact location depends on the platform and on whether a legacy configuration directory exists β€” that’s why you should use this command instead of hard-coding a path, bestie. Don’t do the guessy thing. πŸ™ˆ

It prints the path even if the file doesn’t exist yet, so it’s safe to run before your first glab auth login. Lowkey perfect for pre-setup vibe checks. ✨

Use --dir to print the parent directory instead. And listen: grant write access to that directory rather than to config.yml alone, because glab writes a temporary file in that directory first and then replaces config.yml with it. That’s the whole routine. πŸ’…

Repository-local settings live in the repository’s .git/glab-cli/config.yml, and this command does not report them. Not me being clear about scope. 🫢

If no user configuration file exists, glab falls back to a read-only system-wide one. This command always reports the user location. Periodt. πŸ‘‘

Your own configuration file must not be readable by anyone else, so it needs mode 600. A system-wide one, in a directory listed in XDG_CONFIG_DIRS, is read whatever its read permissions are, but it’s refused if it’s writable by group or others.

bestie, mode 600 is not a suggestion. It’s the vibe check for your own config file. πŸ”₯

πŸŽ€ OPTIONS πŸŽ€

  • --dir[=false] β€” prints the configuration directory instead of the configuration file. It’s the β€œshow me the folder, not the file” button. πŸŽ€

πŸ’– OPTIONS INHERITED FROM PARENT COMMANDS πŸ’–

  • -h, --help[=false] β€” shows help for this command. The classic. ✨

🌈 EXAMPLE 🌈

# Print the path to the global configuration file
glab config path

# Print the directory that holds the configuration file
glab config path --dir

# Open the configuration file in an editor
$EDITOR "$(glab config path)"

πŸ¦‹ SEE ALSO πŸ¦‹

  • glab-config(1) β€” go hang with the parent command page. 🫢

That’s the whole page, bestie. This glab(1) moment was Auto generated by spf13/cobra, dated Nov 2026. Slay. πŸ’–

πŸ“¦ where this page comes from