jj-evolog(1)

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

jj-evolog(1) — the glow-up history of ur change 💅✨

okay so real talk: this is jj evolog, a page from the General Commands Manual, section 1. bestie, it's the receipts page for one single change — where it's been, who it used to be, all of it. 🎀

✨ NAME ✨

jj-evolog — show how a change has evolved over time 🦋

✨ SYNOPSIS ✨

jj evolog [-r|--revisions] [-R|--repository] [--ignore-working-copy]
[-n|--limit] [--no-integrate-operation] [--reversed] [-G|--no-graph]
[--ignore-immutable] [--at-operation] [-T|--template] [--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] [-h|--help]

🌸 DESCRIPTION 🌸

Show how a change has evolved over time ⏳

So like, this lists the previous commits that a change has pointed to. The current commit of a change evolves whenever the change gets updated, rebased, etc. — think of it as the change's main character arc, and evolog is the recap episode. 👑

💖 OPTIONS 💖

  • -r, --revisions <REVSETS> [default: @] — follow changes from these revisions 👀
  • -n, --limit <LIMIT> — limit how many revisions get shown. ngl the ordering matters here: it's applied after revisions are reordered topologically, but before being reversed. 🫶
  • --reversed — show revisions in the opposite order (older revisions first) 🔄
  • -G, --no-graph — show a flat list of revisions instead of a graph 📋
  • -T, --template <TEMPLATE> — render each revision using the given template ✨

All 0-argument methods of the CommitEvolutionEntry type are available as keywords in the template expression. See jj help -k templates for more information.

If not specified, this defaults to the templates.evolog setting.

The docs live at https://docs.jj-vcs.dev/latest/templates/#commitevolutionentry-type for CommitEvolutionEntry, and https://docs.jj-vcs.dev/latest/templates/ for templates. 🔗 (yes i'm giving u the links, ur welcome)

  • -p, --patch — show patch compared to the previous version of this change 🩹

If the previous version has different parents, it will be temporarily rebased to the parents of the new version, so the diff is not contaminated by unrelated changes. (iconic behaviour honestly — no cross-talk in my diffs pls 💅)

  • -h, --help — print help (see a summary with -h) 🙋‍♀️

🎀 DIFF FORMATTING OPTIONS 🎀

  • -s, --summary — for each path, show only whether it was modified, added, or deleted 📝
  • --stat — show a histogram of the changes 📊
  • --types — for each path, show only its type before and after 🔤

The diff is shown as two letters. The first letter indicates the type before and the second letter indicates the type after. - indicates that the path was not present, F represents a regular file, L represents a symlink, C represents a conflict, and G represents a Git submodule.

  • --name-only — for each path, show only its path 🏷️

Typically useful for shell commands like:

jj diff -r @- --name-only | xargs perl -pi -e's/OLD/NEW/g'
  • --git — show a Git-format diff 🐙
  • --color-words — show a word-level diff with changes indicated only by color 🌈
  • --tool <TOOL> — generate diff by external command 🛠️

A builtin format can also be specified as :<name>. For example, --tool=:git is equivalent to --git.

  • --context <CONTEXT> — number of lines of context to show 🔍
  • --ignore-all-space — ignore whitespace when comparing lines 🫥
  • --ignore-space-change — ignore changes in amount of whitespace when comparing lines 🌬️

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

  • --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. (so it's kinda automatic, no cap)

  • --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. like, fr fr, the push is happening 💀
  • --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. (main character energy: chaotic, technically legal 😌)

  • --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. (u can't mute the important stuff, sorry bestie)

  • --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 that's the whole page, every single flag accounted for, nothing skipped, we ate and left no crumbs 🍓

and for the cute sign-off: this page signs off as evolog on the left and jj-evolog(1) on the right down in the footer — that's the source and the manual name, periodt. no separate date line to give you, so don't come for me 💜🧚

📦 where this page comes from