glab-config

name	glab-config
description	Manage glab CLI configuration using the glab config command. Use this skill whenever the user wants to configure glab settings like the default editor, git protocol, browser, or any glab preference. Trigger on phrases like "configure glab", "set glab editor", "change git protocol to SSH", "edit glab config", "set default browser for glab", or any glab configuration management task.

glab Configuration Management

Use glab config to manage glab's behavior — editor, git protocol, browser, and other preferences. Config is stored in ~/.config/glab-cli/config.yml (global) or .git/glab-cli/config.yml (local, project-specific).

Get a Config Value

glab config get editor
glab config get git_protocol
glab config get browser

Set a Config Value

# Local (project-specific, stored in .git/)
glab config set editor vim
glab config set git_protocol ssh

# Global (applies to all projects)
glab config set -g editor "code --wait"
glab config set -g git_protocol https
glab config set -g browser firefox

Key flag:

• -g / --global write to global config (~/.config/glab-cli/config.yml)

Open Config in Editor

glab config edit          # local config
glab config edit -g       # global config

Common Configuration Keys

Key	Description	Example Values
editor	Default text editor for descriptions	vim, nano, code --wait
git_protocol	Protocol for git operations	ssh, https
browser	Browser for --web flag	firefox, google-chrome, open
visual	Visual editor (used for rich editing)	code --wait
api_host	API endpoint for self-managed instances	gitlab.example.com

Config Precedence

1. Environment variables (highest priority, e.g., GITLAB_TOKEN, GITLAB_HOST)
2. Local config (.git/glab-cli/config.yml)
3. Global config (~/.config/glab-cli/config.yml)

Behavior Guidelines

1. SSH vs HTTPS: Recommend git_protocol = ssh for developers with SSH keys set up — it avoids password prompts. Use https in CI/CD environments.
2. Editor with wait: For editors like VS Code, set editor = code --wait so glab waits for the file to be closed before continuing.
3. Local vs global: Use local config for project-specific overrides (e.g., a project that uses a different GitLab instance). Use global for personal preferences.
4. Self-managed instances: If the user's GitLab is not gitlab.com, configure api_host to point to the correct instance.