glab(1)

okay bestie πŸ’– you're reading the glab(1) manual page for glab-stack-save, and it's giving EXPERIMENTAL energy, so buckle up.

✨ NAME ✨

glab-stack-save β€” save your changes as a new diff. (EXPERIMENTAL)

πŸ¦‹ SYNOPSIS πŸ¦‹

glab stack save [flags]

πŸ’… DESCRIPTION πŸ’…

So here's the vibe: glab stack save adds a new diff to the end of the stack. That new diff becomes a new merge request the next time you run glab stack sync. Slay.

To add your changes to the diff you have checked out instead, use glab stack amend. Different tool, different job, iykyk.

🚨 bestie, 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/.

πŸŽ€ OPTIONS πŸŽ€

  • -a, --all[=false] β€” automatically stage modified and deleted tracked files. no cap.
  • -d, --description="" β€” description of the change.
  • -m, --message="" β€” alias for the description flag.
  • --no-verify[=false] β€” bypass the pre-commit and commit-msg hooks of git-commit(1). bypass era πŸ’…

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • -h, --help[=false] β€” show help for this command.
  • -R, --repo="" β€” select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.

πŸ“ EXAMPLE πŸ“

Bestie, here are the examples so you can copy-paste and thrive:

# Save currently staged changes as diff with description
glab stack save -m "added a function"

# Add specified file to staged changes and save diff
glab stack save added_file

# Add all tracked files to staged changes and save diff
glab stack save -a -m "added a function to exisiting file"

# Add all tracked and untracked files to staged changes and save diff
glab stack save . -m "added new file"

πŸ’œ SEE ALSO πŸ’œ


mwah πŸ’‹ Auto generated by spf13/cobra, dated Nov 2026, and it lives in the glab(1) manual. bye bestie, go save those diffs 🫢✨

πŸ“¦ where this page comes from