jj-undo(1)

💅 jj-undo(1) — the jj undo page, but make it make sense

okay so this is the manual page for jj-undo from the General Commands Manual (yes, that's the manual name, we're being official today 🎀). Strap in bestie, we're learning how to take back the last thing you did. no cap, this one's a lifesaver.

---

✨ NAME ✨

jj-undo — literally just undo the last operation 🫶

---

🌸 SYNOPSIS 🌸

jj undo [--allow-cross-workspace] [-R|--repository]
[--ignore-working-copy] [--no-integrate-operation] [--ignore-immutable]
[--at-operation] [--debug] [--color] [--quiet] [--no-pager] [--config]
[--config-file] [-h|--help]

---

🦋 DESCRIPTION 🦋

Undo the last operation. that's the whole vibe 💫

So here's the tea: if you use this once after a normal (non-undo) operation, it undoes that last operation by restoring its parent. like, rewinding the tape. but if you keep hitting jj undo over and over? it restores increasingly older operations, going further and further back into the past. yes bestie, you can keep going. it's giving time machine energy ⏪✨

There's also a complementary jj redo command that goes the other way — it moves in the direction of the future after one or more jj undos. so undo and redo are literally the main character duo of this whole thing 👑💅

Wanna actually see what you've been doing? Use jj op log to visualize the log of past operations, including a detailed description of any past undo/redo operations. and if you want to be all specific about it, peep jj op restore to explicitly restore an older operation by its id (which you can find in the operation log). iykyk 🧚

vibe check / important: by default, jj undo refuses to undo an operation that was performed in another workspace, since that is usually not what you meant to undo. so if you're like "why isn't this working" — that's why, bestie 😭. Pass --allow-cross-workspace to undo it anyway, or use jj op revert to revert a specific operation.

---

⭐ OPTIONS ⭐

• --allow-cross-workspace — allow undoing an operation that was performed in another workspace. use this when you really mean it 🙈
• -h, --help — print help (see a summary with -h). short version for the girlies in a rush 💨

---

🌈 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's like it knows where home is 🏠💖

• --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. automatic, no extra typing ✨

• --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. lowkey unhinged but okay 💀

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 note note: this does not prevent side effects outside the repo. For example, jj git push --no-integrate-operation will still perform the push. so like, don't think this makes you invisible to the remote, because it does not 😭🔥

• --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. it's giving "i know what i'm doing" energy 💅

This option only affects the check. It does not affect the immutable_heads() revset or the immutable template keyword. just so we're clear ✨

• --at-operation <AT_OPERATION> — operation to load the repo at.

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. adorable little @ 🎀

Use jj op log to find the operation ID you want. Any unambiguous prefix of the operation ID is enough. no need to copy the whole thing, a vibe is sufficient 💜

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. (rarely a reason = you probably don't want this, bestie 🫣)

• --debug — enable debug logging. for when you need to see everything 🔍
• --color <WHEN> — when to colorize output. aesthetic decisions matter 🌈

Possible values:

• always
• never
• debug
• auto

• --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. so it's quiet, not silent 😌🤫

• --no-pager — disable the pager. no scrolling detention for you 🚫📜
• --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. yes, TOML, we love a config language 💖

• --config-file <PATH> — additional configuration files (can be repeated). stack 'em up 📚✨

---

And that's the whole page, bestie 🫶💖 go forth and undo responsibly. this has been undo from jj-undo(1) in the General Commands Manual — signed off with love, sparkles, and absolutely zero regrets about that last operation 🌸🎀🦋