jj-util(1)

✨ jj-util(1) — the General Commands Manual's infrequent-commands bestie ✨

okay so this is the jj-util(1) page from the General Commands Manual, and it's literally the home of infrequently used commands. Think shell-completion generation and other lil' utility moments. Slay. 💖

🌸 NAME 🌸

jj-util — infrequently used commands such as for generating shell completions. Simple as that, no cap. 💅

🎀 SYNOPSIS 🎀

jj util [-R|--repository] [--ignore-working-copy]
[--no-integrate-operation] [--ignore-immutable] [--at-operation]
[--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file]
[-h|--help] <subcommands>

That's the whole vibe: you're calling jj util with the usual global flags and then one of the <subcommands>. 🫶

🦋 DESCRIPTION 🦋

Infrequently used commands such as for generating shell completions. It's giving "you need this sometimes but not every day" energy, and that's valid. ✨

💅 OPTIONS 💅

• -h, --help — Print help (see a summary with '-h'). Iconic. Ask and you shall receive. 👑

🌈 GLOBAL OPTIONS 🌈

These are the big main-character flags that ride along with jj util and friends. 🫶

• -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's lowkey doing the find-the-repo dance for you. 🕵️‍♀️

• --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. 💀 read that again, 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. fr fr, only the check.

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

• --debug — Enable debug logging. not me reaching for this when things get mysterious. 🔍
• --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. the way that it still keeps the useful part is honestly a vibe.

Warnings and errors will still be printed.

• --no-pager — Disable the pager. Sometimes you just want the raw terminal energy. 💅
• --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). obsessed with repeatable flags? same. 🎀

👑 SUBCOMMANDS 👑

These are the lil' side quests living under jj util. Each one has its own page, iykyk. 🧚

• jj-util-backend(1) — Commands relating to the backend used in the current repo
• jj-util-completion(1) — Print a command-line-completion script
• jj-util-config-schema(1) — Print the JSON schema for the jj TOML config format
• jj-util-diff(1) — Compare two files on disk
• jj-util-exec(1) — Execute an external command via jj
• jj-util-gc(1) — Run backend-dependent garbage collection
• jj-util-install-man-pages(1) — Install Jujutsu's manpages to the provided path
• jj-util-markdown-help(1) — Print the CLI help for all subcommands in Markdown
• jj-util-snapshot(1) — Snapshot the working copy if needed

---

and that's the page, bestie! 🫶 footer vibe check: source/version is util, the manual page is jj-util(1), and the date slot is lowkey empty in the source — so we're not inventing one. periodt. 💖✨