glab(1)

glab(1) — the manual page, but make it make sense 💅

okay so bestie, you're looking at the manual for glab — and this specific page is all about glab stack amend. Yes it's experimental. Yes we'll get to that. Buckle up 🎀

---

✨ NAME ✨

glab-stack-amend — save your changes to an existing diff, i.e. the "oops I forgot a thing" command. (EXPERIMENTAL) 🧪

---

✨ SYNOPSIS ✨

glab stack amend [flags]

---

✨ DESCRIPTION ✨

So. You've got a diff checked out, and you've got changes you want to fold into it. This command takes your changes and adds them to that diff. 🫶

Its merge request updates the next time you run glab stack sync — and that same sync also rebases the diffs that come after it. iykyk.

If you'd rather spin up a whole new diff out of your changes instead? That's a different girl. Go use glab stack save for that one. ✨

💀 Real talk: this feature is an experiment and is not ready for production use. It might be unstable, or honestly just get removed at any time, no warning, no text back. For more info, see https://docs.gitlab.com/policy/development_stages_support/. Don't say I didn't tell you, bestie 😭

---

✨ OPTIONS ✨

• -a, --all[=false] — automatically stages your modified and deleted tracked files. Let the command cook for you 🍓
• -d, --description="" — a description of the change. Say what you did, iconically ✍️
• -m, --message="" — literally just an alias for the description flag. Same energy, shorter to type 💅
• --no-verify[=false] — bypasses the pre-commit and commit-msg hooks of git-commit(1). Sneaky. Use with intention 👀
• --reword[=false] — only updates the commit message, stages no files. Message glow-up, zero file drama 🦋

---

✨ OPTIONS INHERITED FROM PARENT COMMANDS ✨

• -h, --help[=false] — show help for this command. When in doubt, ask the manual (that's me, hi 🫶)
• -R, --repo="" — select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. Very "I contain multitudes" of it 🌈

---

✨ EXAMPLE ✨

okay these are genuinely the moves, no cap 🔥

# Amend diff with currently staged changes
glab stack amend -m "Fix a function"

# Add specified file to staged changes and amend diff
glab stack amend newfile -m "forgot to add this"

# Add all tracked files to staged changes and amend diff
glab stack amend -a -m "fixed a function in exisiting file"

# Add all tracked and untracked files to staged changes and amend diff
glab stack amend . -m "refactored file into new files"

# Reword the commit message without adding any files
glab stack amend --reword -m "updated commit message"

(psst — that exisiting typo in the third example? that's the original's typo, not mine, and I am not touching it. Character for character, bestie. 🎀)

---

✨ SEE ALSO ✨

• glab-stack(1) — the parent command, the main character of this whole saga 👑

---

---

🌸 okay that's the whole page! this manual page is Auto generated by spf13/cobra, dated Nov 2026, and it's the glab(1) manual. go amend your diffs, have fun, and remember: it's experimental, so stay hydrated and back up your stuff 💖✨🦋