jj-util-backend-name(1)

✨ jj-util-backend-name ✨

okay bestie, listen 💖 this is the manual page for jj-util-backend-name(1), living in the General Commands Manual section of your friendly neighbourhood jj docs. it's tiny, it's cute, it does exactly one thing, and it does it flawlessly. no notes. 🎀

---

🌸 NAME 🌸

jj-util-backend-name — print the name of the backend used in the current repo 🦋

---

🫶 SYNOPSIS 🫶

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

---

💅 DESCRIPTION 💅

Print the name of the backend used in the current repo. that's it. that's the whole thing. she's a one-trick pony and the trick is slay ✨

---

👑 OPTIONS 👑

• -h, --help — print help (see a summary with -h)

---

🌈 GLOBAL OPTIONS 🌈

• -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 the current working directory. it's giving "where's my repo" energy and honestly it always finds it.

• --ignore-working-copy — don't snapshot the working copy, and don't update it 🙈

so, normally Jujutsu snapshots your working copy at the beginning of every single command. every one. it's very on top of things. and the working copy also gets updated at the end of the command, if the command modified the working-copy commit (@). if you want to skip the snapshotting and instead look at a possibly stale working-copy commit, this is your girl. 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.

heads up bestie ⚠️ note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. no take-backs, the push is real.

• --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. living dangerously, love that for you.

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 — no need to type the whole thing, we're not monsters.

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. chaos option, honestly 🔥

• --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. she stays loud when it matters 💜

• --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, no cap. short, sweet, iconic. now go find out what backend your repo is running, you deserve to know. 💖✨

mwah 💋 — this was jj-util-backend-name(1) from the General Commands Manual, and the page signs off as name / jj-util-backend-name(1). that's the whole footer, that's the whole vibe, we are so done here. 🦋🎀