jj-operation-abandon(1)

💅 NAME 💅

jj-operation-abandon — bestie, this is the one that lets you abandon operation history. Like, throw it away. Gone. Bye. 🗑️✨

This page lives in the General Commands Manual section, and yeah it's jj operation abandon's very own page, we're just vibing here together 🫶

---

🌸 SYNOPSIS 🌸

jj operation abandon [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <OPERATION>

okay so that's a LOT of brackets but it's giving "flexible, actually" 💁‍♀️

---

✨ DESCRIPTION ✨

Abandon operation history. That's the whole thing. That's the assignment and it ate. 🔥

Okay but fr fr, here's the tea. If you want to discard old operation history, you do this:

jj op abandon ..<operation ID>

What that does: it abandons the operation you specified plus all of its ancestors — the whole family tree, no cap. And the descendants? They don't get abandoned, bestie, they get reparented onto the root operation. They're fine, they just moved in with the root. 💖

Now, if what you actually want is to toss out your recent operations instead, the move is a two-step combo, and honestly it's kind of iconic:

1. jj op restore <operation ID>
2. jj op abandon <operation ID>..@-

Do them in that order, pls and thank you 🙏

Also lowkey important: previous versions of a change (or predecessors, same vibe) get discarded too if they become unreachable from the operation history. So the abandoned operations, the commits, and all the other unreachable objects can later be garbage collected by using the jj util gc command. Like, that's the cleanup crew finally showing up. 🧹✨

Not me telling you that once something's unreachable, the garbage collector can come for it. That's just how it works. 🫣

---

🎀 OPTIONS 🎀

• -h, --help — Print help (see a summary with -h). Short version if you ask nicely with the lil -h. 💅
• <OPERATION> — The operation or operation range to abandon. Yeah, this one's required, bestie, you gotta tell it what to abandon. 🫶

---

🌈 GLOBAL OPTIONS 🌈

• -R, --repository <REPOSITORY> — Path to repository to operate on. By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. It just goes looking up the tree like "where's the repo, where's the repo" 🦋
• --ignore-working-copy — Don't snapshot the working copy, and don't update it. By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (@). If you want to avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use --ignore-working-copy. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy. Loading the repository at a specific operation with --at-operation implies --ignore-working-copy. ✨
• --no-integrate-operation — Run the command as usual but don't integrate any operations. When this option is given, the operations will still be created as usual but they will not be integrated to the operation log. The working copy will also not be updated. The command will print the resulting operation ID. You can pass that to e.g. jj --at-op to inspect the resulting repo state, or you can pass it to jj op restore to restore the repo to that state. You can also pass the ID to jj op integrate to integrate the operation. Note that this does not prevent side effects outside the repo. For example, jj git push --no-integrate-operation will still perform the push. 😳 like yeah it's literally still gonna push, bestie.
• --ignore-immutable — Allow rewriting immutable commits. By default, Jujutsu prevents rewriting commits in the configured set of immutable commits. This option disables that check and lets you rewrite any commit but the root commit. This option only affects the check. It does not affect the immutable_heads() revset or the immutable template keyword. ⚠️ yes it really does only affect the check, it's not out here changing revsets.
• --at-operation <AT_OPERATION> — Operation to load the repo at. By default, Jujutsu loads the repo at the most recent operation, or at the merge of the divergent operations if any. You can use --at-op=<operation ID> to see what the repo looked like at an earlier operation. For example jj --at-op=<operation ID> st will show you what jj st would have shown you when the given operation had just finished. --at-op=@ is pretty much the same as the default except that divergent operations will never be merged. Use jj op log to find the operation ID you want. Any unambiguous prefix of the operation ID is enough. When loading the repo at an earlier operation, the working copy will be ignored, as if --ignore-working-copy had been specified. It is possible to run mutating commands when loading the repo at an earlier operation. Doing that is equivalent to having run concurrent commands starting at the earlier operation. There's rarely a reason to do that, but it is possible. 🕰️ time travel but make it version control.
• --debug — Enable debug logging. For when you wanna see Everything. 🔍
• --color <WHEN> — When to colorize output. Possible values:
  • always
  • never
  • debug
  • auto

it's giving aesthetic control 💅🌈

• --quiet — Silence non-primary command output. For example, jj file list will still list files, but it won't tell you if the working copy was snapshotted or if descendants were rebased. Warnings and errors will still be printed. 🤫 still loud when it matters.
• --no-pager — Disable the pager. No scrolling hotel, just raw output straight to your terminal. 🫶
• --config <NAME=VALUE> — Additional configuration options (can be repeated). The name should be specified as TOML dotted keys. The value should be specified as a TOML expression. If string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted. ✨ repeat it as many times as your heart desires.
• --config-file <PATH> — Additional configuration files (can be repeated). 📁 stack 'em up.

---

🌟 little reminder bestie: everything above applies to jj operation abandon, and honestly it's got main character energy for a command that just... abandons things. 💀

---

and that's the whole page, pookie!! 🎀 this was abandon from jj-operation-abandon(1), sitting pretty in the General Commands Manual. slay, go abandon some operation history responsibly, and remember — you can always gc later. 💖✨🦋🌸👑