jj-util-backend(1)

💖 jj-util-backend — the manual, but make it cute 💖

okay bestie, so this is the manual page for jj-util-backend(1) from the General Commands Manual. Welcome to the backend-themed section of your fave version control tool 🎀

---

✨ NAME ✨

jj-util-backend — commands relating to the backend used in the current repo 🫶

---

🌸 SYNOPSIS 🌸

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

---

🦋 DESCRIPTION 🦋

Commands relating to the backend used in the current repo. that's it, that's the whole vibe 💅

---

⭐ OPTIONS ⭐

• -h, --help — prints the help, and if you pass the short -h you get the summary version instead of the whole novel. iykyk 📖

---

👑 GLOBAL OPTIONS 👑

these ones work everywhere, not just here — main character energy for real 💜

• -R, --repository <REPOSITORY> — path to the repository you wanna operate on.

by default, Jujutsu goes hunting for the closest .jj/ directory in an ancestor of your current working directory. like it's literally climbing your file tree looking for home 🏠

• --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 it also updates the working copy at the end of the command, if the command modified the working-copy commit (@). so if you wanna 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 like, package deal, 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. so like, careful bestie, it's giving "not everything is undone" 🙈

• --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. iconic behavior tbh ⭐

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 🐛
• --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. so like, you can't hide those, 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) 📂

---

🎀 SUBCOMMANDS 🎀

• jj-util-backend-name(1) — print the name of the backend used in the current repo. that's the whole job and she does it flawlessly 💖

---

and that's the page, bestie!! this one's from the backend source, dated — ngl the date slot is just sitting there empty in this render 🙈 — and it's manual page jj-util-backend(1). go forth and check your backend, you absolute genius 🌟💅🦋