glab(1)

📦
version 1.128.0 · 10 versions
, in arch rolling

💖 glab(1) — the manual page, bestie 💖

okay so this is the glab(1) manual page, and today’s main character is glab-stack — the stacked-diffs command. Yes, it’s giving “experimental but iconic.” 💅

✨ NAME ✨

glab-stack — Create, manage, and work with stacked diffs. (EXPERIMENTAL) 🧚

🌸 SYNOPSIS 🌸

glab stack  [flags]

🦋 DESCRIPTION 🦋

Use stacked diffs to split a feature into small, dependent changes. Reviewers can review and merge earlier changes while you keep building on top of them. Slay, honestly. 💖

Each stack contains diffs. Each diff is one commit on its own branch, built on the branch of the previous diff. When you run glab stack sync, each diff becomes a merge request that targets the branch of the previous diff. The first diff targets the base branch. No cap, that’s the whole stacked-diff vibe. ✨

The glab stack commands act on the stack you last created or switched to, regardless of which branch you have checked out. Lowkey convenient, highkey important. 🫶

🚨 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/. Bestie, please read that warning fr fr. 💀

💅 OPTIONS 💅

  • -R, --repo="" — Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. 🎀

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

  • -h, --help[=false] — Show help for this command. Our little helper icon. 🌟

🌈 EXAMPLE 🌈

glab stack create cool-new-feature
glab stack sync

🔥 SEE ALSO 🔥

Auto generated by spf13/cobra, dated Nov 2026, and this is the glab(1) page. Byeee, go stack those diffs responsibly 🫶💜

📦 where this page comes from