STG-GOTO(1)

πŸ’… STG-GOTO(1) β€” like, the StGit Manual, bestie ✨

okay so welcome to stg-goto, one of the little icons of the StGit manual πŸŽ€ she's short, she's sweet, she gets you where you need to go. let's gooo πŸ¦‹


🌸 NAME 🌸

stg-goto β€” go to a patch by pushing or popping as necessary, no cap πŸ’…


✨ SYNOPSIS ✨

stg goto [OPTIONS] <patch>

🫢 DESCRIPTION 🫢

Go to patch by pushing or popping as necessary. that's it. that's the whole vibe. she pushes, she pops, you arrive. main character energy fr fr πŸ‘‘


πŸ’– OPTIONS πŸ’–

  • -k, --keep β€” keep the local changes. your stuff stays, bestie 🩷
  • -m, --merged β€” check for patches merged upstream. very "let me just verify" of her πŸ”
  • --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. slay, a lil time travel moment ⏰✨
  • --conflicts[=<policy>] β€” either "allow" or "disallow" pushing a patch with conflicts. pick your fighter πŸ₯Š

using --conflicts=allow (or just --conflicts) allows pushing a patch that may result in unresolved merge conflicts. the patch will be pushed and files with conflicts will be left with conflict markers to be resolved manually; or the operation undone with stg undo --hard. this is the default behavior and also corresponds to the "stgit.push.allow-conflicts" variable being set to "true". 😭 yes you're gonna see conflict markers and yes you gotta deal with them yourself, i don't make the rules

using --conflicts=disallow disallows pushing any patch that would result in merge conflicts. the operation will stop on the last patch that can be pushed without conflicts. this behavior can be configured by setting "stgit.push.allow-conflicts" to "false". she'll just stop and refuse to go further, and honestly? boundaries. respect them πŸ’€

ngl the conflict thing is the one to actually read twice β€” allow is the default, and it will leave you with conflict markers in your files to sort out manually (or you bail with stg undo --hard). not a vibe to be surprised by it πŸ™ˆ

πŸ‘‘ STGIT πŸ‘‘

part of the StGit suite β€” see stg(1) πŸ§šβ€β™€οΈ


that's the whole page, bestie, go forth and goto πŸ’œ

StGit 2.7.0 Β· 10/17/2026 Β· STG-GOTO(1) β€” mwah, thanks for reading, ily, see you in the next manpage πŸ“πŸ’–

πŸ“¦ where this page comes from