STG-POP(1)

🌸 stg-pop β€” StGit Manual, bestie edition 🌸

omg hi πŸ’– welcome to STG-POP(1), aka the stg-pop page from the StGit Manual. it’s giving β€œunapply those patches with main character energy,” and we’re gonna walk through it together 🫢✨


🌈 NAME 🌈

stg-pop β€” Pop (unapply) one or more applied patches πŸ’…


✨ SYNOPSIS ✨

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

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: you’ve got applied patches, and stg pop pops them β€” aka unapplies one or more of them πŸŽ€βœ¨

By default, the topmost applied patch is popped. yes bestie, just the top one gets the vibe check first πŸ’…

If ranges of patches are specified, pop and push operations are performed such that only the patches specified on the command line are unapplied at the end of the operation. It is possible for some of these intermediate push operations to fail due to conflicts if patches are popped out of last-pushed first-popped order 😭 so yeah, the middle of that whole situation can get spicy in a conflict way. fr fr.


πŸ’– OPTIONS πŸ’–

  • -a, --all β€” pop all applied patches, the whole squad, every last one 🌈
  • -n <number>, --number=<number> β€” pop the specified <number> of patches. A negative number indicates to pop all but that number of patches β€” yes, negative math is invited to the function πŸ’…
  • -s, --spill β€” keep patches’ modifications in the index and worktree after popping 🫢
  • -k, --keep β€” keep the local changes ✨

πŸ‘‘ STGIT πŸ‘‘

Part of the StGit suite - see stg(1) πŸ’œ go read stg(1) for the whole suite, iykyk.


xoxo, this page is from StGit 2.7.0, dated 10/17/2026 🫢 the footer said STG-POP(1) and she absolutely ate πŸ’…βœ¨ periodt.

πŸ“¦ where this page comes from