STG-SPILL(1)

🌸 STG-SPILL(1) 🌸

okay so bestie, welcome to the StGit Manual page for stg-spill β€” literally one of the cutest little commands in the whole suite πŸ’…


✨ NAME ✨

stg-spill β€” spill changes from the topmost patch πŸ«—


✨ SYNOPSIS ✨

stg spill [OPTIONS] [path]...

✨ DESCRIPTION ✨

So here's the vibe: stg spill takes changes from the topmost patch and spills them out. The changes get removed from the patch, but β€” and this is the iconic part β€” they stay in the index and worktree. Nothing is lost, it's just relocated πŸ’–

Why would you even want that? Because spilling a patch is lowkey useful for reselecting the files/hunks that end up included in the patch. Like, you dump everything out, then carefully pick what goes back in. Curated. Main character energy πŸ‘‘


✨ OPTIONS ✨

  • -a <note>, --annotate=<note> β€” drops a little note into the patch log entry. annotate your patch, bestie, future you will thank you πŸŽ€
  • -r, --reset β€” also resets the index, so the patch's changes only remain in the worktree. Fr fr: without this option, the patch's changes are in both the index and worktree. With it, index says "not me" πŸ™ˆ
  • --committer-date-is-author-date β€” instead of using the current time as the committer date, use the author date of the commit as the committer date. same energy, zero clock drama ⭐

✨ STGIT ✨

it's part of the StGit suite β€” see stg(1) for the whole fam 🫢


quick vibe check: spilling removes the changes from the patch, but they remain in the index and worktree β€” so don't panic, nothing vanished, it's just hanging out elsewhere ✨

mwah, that's the page πŸ’‹ this was served fresh from StGit 2.7.0, dated 10/17/2026 β€” see you in the next manpage, bestie πŸŒˆπŸ¦‹

πŸ“¦ where this page comes from