glab(1)

πŸ¦‹ NAME πŸ¦‹

glab-stack-switch β€” Switch between stacks. (EXPERIMENTAL)

okay so you're reading the glab(1) manual page for glab stack switch, and honestly? main character energy. this is the stack switcher, bestie, and yes it's marked EXPERIMENTAL β€” more on that in a sec πŸ’–

🌈 SYNOPSIS 🌈

glab stack switch [stack-name] [flags]

πŸ’– DESCRIPTION πŸ’–

If you do not provide a stack name, the command shows a list of stacks for you to choose from. cute, right? no guessing required, just pick your fave ✨

After you switch, use glab stack move to check out a diff in the new stack. that's the follow-up move, iykyk πŸŽ€

🚨 experiment alert: this feature is an experiment and is not ready for production use. It might be unstable or removed at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/. fr fr, do not build your whole prod workflow on it yet πŸ’€

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

these flags come inherited from the parent commands, and they're lowkey important:

  • -h, --help[=false] β€” Show help for this command. when in doubt, ask for help, bestie 🫢
  • -R, --repo="" β€” Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. so many valid ways to point at a repo, we love options πŸ’…

πŸ”₯ EXAMPLE πŸ”₯

run these exactly, bestie:

# Interactively pick from the list of available stacks.
glab stack switch

# Switch to a specific stack by name.
glab stack switch <stack-name>

πŸ‘‘ SEE ALSO πŸ‘‘


okay that's the whole vibe πŸ“ sign-off time: this page was auto generated by spf13/cobra, dated Nov 2026, and it's part of the glab(1) manual. mwah, bestie πŸ’œ

πŸ“¦ where this page comes from