jj-operation-log(1)

📦
version 0.46.0 · 2 versions
, in arch rolling, nixpkgs unstable

✨ jj-operation-log(1) ✨ (the operation log, bestie)

okay so this is the manpage for jj operation log, from the General Commands Manual — yes it's that Jujutsu, the VCS that ate and left no crumbs 💅. Buckle up, we're reading the receipts of your whole repo's history 🎀

🌸 NAME 🌸

jj-operation-log — Show the operation log 🫶

🦋 SYNOPSIS 🦋

jj operation log [-n|--limit] [-R|--repository] [--ignore-working-copy]
[--reversed] [-G|--no-graph] [--no-integrate-operation]
[--ignore-immutable] [-T|--template] [--at-operation] [-d|--op-diff]
[--debug] [-p|--patch] [--color] [-s|--summary] [--quiet] [--stat]
[--no-pager] [--types] [--config] [--name-only] [--config-file] [--git]
[--color-words] [--tool] [--context] [--ignore-all-space]
[--ignore-space-change] [--show-changes-in] [-h|--help]

💖 DESCRIPTION 💖

Show the operation log. That's it, that's the vibe ✨

But lowkey there's a whole thing happening behind the scenes: like every other command, jj op log snapshots the current working-copy changes and reconciles divergent operations before it does anything. Main character energy, honestly.

Want to peek at the current state without mutating anything? Use --at-op=@ --ignore-working-copy. No cap, that's the move 🙈

👑 OPTIONS 👑

  • -n, --limit <LIMIT> — Caps how many operations you see. Applied after operations are reordered topologically, but before being reversed. Order of operations matters, iykyk 🧚
  • --reversed — Flips it: older operations first. Chronological girlies rise 🌈
  • -G, --no-graph — Drops the graph and gives you a flat list of operations instead. Simple. Clean. Slay 💅
  • -T, --template <TEMPLATE> — Renders each operation using the template you hand it. All 0-argument methods of the [Operation type][Operation] are available as keywords in the template expression. Peep jj help -k templates for the full lore. If you don't specify anything, it defaults to the templates.op_log setting 🎀
  • -d, --op-diff — Shows the changes to the repository at each operation. The receipts, fr fr 🔥
  • -p, --patch — Shows a patch of modifications to changes (and yes, it implies --op-diff). Heads up: if the previous version has different parents, it gets temporarily rebased to the parents of the new version, so the diff isn't contaminated by unrelated changes. Considerate king behavior 👑
  • -h, --help — Prints help (see a summary with -h). Classic 🫶

🍓 DIFF FORMATTING OPTIONS 🍓

  • -s, --summary — For each path, shows only whether it was modified, added, or deleted. The ✨tl;dr✨ of diffs.
  • --stat — Shows a histogram of the changes. Numbers! Beautiful! Ate 💯
  • --types — For each path, shows only its type before and after. The diff appears as two letters: the first letter is the type before, the second is the type after. - means the path wasn't present, F is a regular file, L is a symlink, C is a conflict, and G is a Git submodule. Little alphabet soup, but make it informative 🧚
  • --name-only — For each path, shows only its path. Typically useful for shell commands like: jj diff -r @- --name-only | xargs perl -pi -e's/OLD/NEW/g' — copy that exactly, bestie, character for character 💖
  • --git — Shows a Git-format diff 🦋
  • --color-words — Shows a word-level diff where changes are indicated only by color. Very demure, very mindful 🌸
  • --tool <TOOL> — Generates the diff by an external command. You can also name a builtin format as :<name> — for example, --tool=:git is equivalent to --git ✨
  • --context <CONTEXT> — Number of lines of context to show 👀
  • --ignore-all-space — Ignores whitespace when comparing lines 🙈
  • --ignore-space-change — Ignores changes in the amount of whitespace when comparing lines. Subtle but iconic 💅
  • --show-changes-in <REVSETS> — Shows only changed revisions matching the given revset expression. If no revisions are specified, this defaults to the revsets.op-diff-changes-in setting 🎀

🌟 GLOBAL OPTIONS 🌟

  • -R, --repository <REPOSITORY> — Path to the repository to operate on. By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory 🔍
  • --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, and 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 and instead see a possibly stale working-copy commit, this is your flag. It's useful e.g. in a command prompt, especially if you have another process that commits the working copy. Also: loading the repository at a specific operation with --at-operation implies --ignore-working-copy ⭐
  • --no-integrate-operation — Runs the command as usual but doesn't integrate any operations. The operations are still created as usual, they're just not integrated into the operation log — and the working copy won't be updated either. 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 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.
Careful bestie 😭 this does not prevent side effects outside the repo. For example, jj git push --no-integrate-operation will still perform the push. Fr fr.
  • --ignore-immutable — Allows 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 only affects the check — it does not affect the immutable_heads() revset or the immutable template keyword 🙅‍♀️
  • --at-operation <AT_OPERATION> — The 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 while 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 💀

  • --debug — Enables debug logging 🐛
  • --color <WHEN> — When to colorize output. Possible values:
    • always
    • never
    • debug
    • auto
  • --quiet — Silences 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 ⚠️
  • --no-pager — Disables the pager 🙈
  • --config <NAME=VALUE> — Additional configuration options (can be repeated). The name should be specified as TOML dotted keys, and the value should be specified as a TOML expression. If the 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) 📁

🧚 a little footnote moment 🧚

The [Operation type][Operation] link lives at https://docs.jj-vcs.dev/latest/templates/#operation-type and the templates docs at https://docs.jj-vcs.dev/latest/templates/ — go read them, they're giving study material 💜

And that's the whole page, bestie 🫶 — this was jj-operation-log(1) from the General Commands Manual, filed under the log section, dated whatever your man page says at the bottom (check your local copy, she's got the timestamp). Go log some operations. Periodt. 💅✨

📦 where this page comes from