STG-COMMIT(1)

💅 STG-COMMIT 💅

okay so bestie, welcome to a page straight out of the StGit Manual — this one's stg-commit, and it's genuinely one of the most satisfying commands in the whole suite. no cap.

---

✨ SYNOPSIS ✨

stg commit [OPTIONS] [patch]...
stg commit [OPTIONS] -n <number>
stg commit [OPTIONS] --all

that's literally it. three whole ways to glow up your patches into the base. 🫶

---

🌸 DESCRIPTION 🌸

so here's the vibe: stg-commit finalizes one or more patches into the base of the current stack and then removes them from the series. it's giving graduation ceremony 🎓 — the patch has finished its character arc and no longer needs to be managed with StGit.

this is the exact opposite of stg-uncommit(1), so if commit is "congrats you're done 💖", uncommit is "jk come back 😭".

run this when a patch is completed and you're ready to stop babysitting it with StGit. that's the whole point.

by default, the bottommost patch gets committed. simple, no drama. but if you pass patch names, the stack gets rearranged so those patches are sitting at the bottom first, and then they get committed. lowkey a glow-up rearrangement situation, but that's the deal. ✨

and the -n/--number option tells it how many applied patches to commit (counting from the bottom of the stack, obviously). if you hand it -a/--all, then all applied patches get committed. all of them. the whole friend group. 👑

---

🎀 OPTIONS 🎀

• -n <number>, --number=<number> — commit the specified number of applied patches. counted from the bottom of the stack, bestie, so be careful with your numbers 💅
• -a, --all — commit all applied patches. every single one. main character energy 🔥
• --allow-empty — allow empty patches to be committed. yes, that needed its own flag 🙈

---

🦋 STGIT 🦋

it's all part of the StGit suite — go look at stg(1) for the full picture, iykyk 💜

---

okay that's the whole page, mwah 🍓 — this was StGit 2.7.0, dated 10/17/2026, and you absolutely ate that read. go commit something iconic ✨👑