jj-prev(1)

✨ jj-prev(1) ✨

okay bestie, pull up a chair 🫶 this is the page for jj-prev from the General Commands Manual, and by the end of it you're gonna be moving your working copy around like it's nothing. no cap.

---

💖 NAME 💖

jj-prev — change the working copy revision relative to the parent revision

🎀 SYNOPSIS 🎀

jj prev [-e|--edit] [-R|--repository] [--ignore-working-copy]
[-n|--no-edit] [--conflict] [--no-integrate-operation]
[--ignore-immutable] [--at-operation] [--debug] [--color] [--quiet]
[--no-pager] [--config] [--config-file] [-h|--help] [OFFSET]

🦋 DESCRIPTION 🦋

Change the working copy revision relative to the parent revision. that's the whole mission statement, and honestly? iconic.

The command creates a new empty working copy revision that is the child of an ancestor offset revisions behind the parent of the current working copy. so like… you're hopping your @ back up the family tree by offset steps and letting it settle there as a fresh empty commit. the way that works out is genuinely so satisfying 💅

For example, when the offset is 1:

D @      D |/       | A   =>   A @ |        |/ B        B

If --edit is passed, the working copy revision is changed to the parent of the current working copy revision. (yes bestie, that is a different thing — heads up.)

D @      D |/       | C   =>   @ |        | B        B | | A        A

💅 OPTIONS 💅

• -e, --edit — Edit the parent directly, instead of moving the working-copy commit. Takes precedence over config in ui.movement.edit; i.e. will negate ui.movement.edit = false. so this flag wins the argument, periodt.
• -n, --no-edit — The inverse of --edit. Takes precedence over config in ui.movement.edit; i.e. will negate ui.movement.edit = true. yeah it's literally just the mirror of the one above, she said what she said.
• --conflict — Jump to the previous conflicted ancestor. skipping straight to the drama 🍓
• -h, --help — Print help (see a summary with -h).
• [OFFSET] [default: 1] — How many revisions to move backward. Moves to the parent by default. so if you don't say a number, she assumes 1, no questions asked.

🌈 GLOBAL OPTIONS 🌈

these ones aren't jj-prev's alone bestie, they're the shared lore of the whole toolset.

• -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. so it goes hunting upward for you, lowkey sweet.
• --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. ✨ surprise inheritance ✨

• --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. 🔥 careful bestie, the push is pushing regardless.

• --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. so it's a check-skipper, not a history-rewriter of the rulebook itself.

• --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. 🙈 like… girl. it's possible. that's all we're gonna say.

• --debug — Enable debug logging. for when you want the tea in full detail.
• --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. she's quiet, not silent — the important stuff still gets through 💜

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

---

and that's the whole page bestie, we ate 💅 this is jj-prev as tagged in the General Commands Manual — source/version stamp prev, reference jj-prev(1), in all her glory. go move that @ around, you got this 🫶✨👑