jj-operation-revert(1)

🎀 jj-operation-revert — NAME 🎀

okay bestie, so this is jj-operation-revert(1), a General Commands Manual page from the Jujutsu fam. and what it does is: Create a new operation that reverts an earlier operation. yes ma'am, undo for your undo log 💖

---

✨ SYNOPSIS ✨

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

---

🦋 DESCRIPTION 🦋

Create a new operation that reverts an earlier operation. literally what it says on the tin, no cap.

so the vibe here is: this reverts an individual operation by applying the inverse of the operation. one operation. just that one. 🌸

---

💅 OPTIONS 💅

• --what <WHAT> [default: repo,remote-tracking] — what portions of the local state to restore. and yes, it can be repeated, so stack 'em up if you want them all.

bestie this one is EXPERIMENTAL — tread carefully, it's giving beta energy 🙈

Possible values, one by one:

• repo: the jj repo state and local bookmarks 📒
• remote-tracking: the remote-tracking bookmarks. Do not restore these if you'd like to push after the undo — like, if you're planning to push afterwards, skip this one fr fr.

• -h, --help — print help. and pro tip: see a summary with -h, because less is more sometimes ✨
• [OPERATION] [default: @] — the operation to revert. the one you're sending back to where it came from 😭

use jj op log to find an operation to revert. that's the treasure map, go forth 🗺️

---

👑 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 giving "don't worry, I'll find it" energy 🫶

• --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. they're a package deal, periodt 💅

• --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. so like, the thing happens, but it's not filed anywhere 📁

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. so many doors opening bestie 🚪✨

note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. so yeah, the push really does push 😭

• --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. it just turns off the bouncer, it doesn't change the guest list 💀

• --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.

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough — short queen behavior, love that for you 👑

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. (highkey chaotic, but nobody's stopping you 🌈)

• --debug — enable debug logging. for when you wanna see everything 🔍
• --color <WHEN> — when to colorize output.

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. it's the "just the facts" setting 🤫

warnings and errors will still be printed. you can't mute those, sorry babe.

• --no-pager — disable the pager. no more less, just 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. TOML girlies rise up 💜

• --config-file <PATH> — additional configuration files (can be repeated).

---

and that's the whole page, bestie!! 🫶 this lil cutie comes to you from the Jujutsu manual set — the footer stamps it with revert and the manual name jj-operation-revert(1), so that's the ✨source and version✨ flex at the bottom. stay revert-y, go undo something iconic, and remember: vim be upon ye 💖✨🎀🦋🌸💅