jj-redo(1)

💅 jj-redo(1) — Redo the most recently undone operation ✨

okay bestie, welcome to jj-redo(1) from the General Commands Manual 🫶 this is the page for jj redo, and it’s literally the “put it back” button for your last undo. Let’s get into it 💖

---

🌸 NAME

jj-redo — redo the most recently undone operation, periodt.

---

✨ SYNOPSIS

jj redo [--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

Redo the most recently undone operation 💫

This is the natural counterpart of jj undo. Repeated invocations of jj undo and jj redo act similarly to Undo/Redo commands in a text editor. No cap, it’s giving very much Ctrl+Z but for your repo 🎀

Use jj op log to visualize the log of past operations, including a detailed description of any past undo/redo operations. See also jj op restore to explicitly restore an older operation by its id (available in the operation log). iykyk 👑

By default, jj redo refuses to redo an undo-operation that was performed in another workspace, since that is usually not what you meant to redo. Pass --allow-cross-workspace to redo it anyway, or use jj op revert to revert a specific undo operation.

---

🎀 OPTIONS

• --allow-cross-workspace — allow redoing an undo-operation that was performed in another workspace. Like, yes, even that one from the other workspace 💅
• -h, --help — print help (see a summary with -h).

---

🌈 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. Cute little repo-hunting behavior fr fr 🧚
• --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. So yeah, read that twice 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. 👑
• --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. 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 tea ☕✨
• --debug — enable debug logging.
• --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. Warnings and errors will still be printed. quiet luxury but for CLI output 💅
• --no-pager — disable the pager.
• --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. 🍓
• --config-file <PATH> — additional configuration files (can be repeated).

---

okay bestie, that’s the whole jj-redo(1) moment 💖 — source/manual: General Commands Manual, page: jj-redo(1), footer tea: redo + jj-redo(1); no extra date/version numbers were in the original footer, so I’m not making any up 🫶✨