jj-version(1)

💖 jj-version — bestie's guide to the version command 💅

okay so real quick, this page lives in section 1 of the general commands manual and it's literally called jj-version. grab a strawberry 🍓 and let's go.

✨ NAME ✨

jj-version — display version information 👑

🌸 SYNOPSIS 🌸

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

🦋 DESCRIPTION 🦋

Display version information 💖

that's it. that's the whole job. no cap.

🎀 OPTIONS 🎀

• -h, --help — print the help. heads up bestie, this one shows you a summary when you use -h.

💜 GLOBAL OPTIONS 💜

these ones are the big shared ones, so they show up across the whole crew, not just here.

• -R, --repository <REPOSITORY> — the path to the repository you wanna operate on 🫶 by default, Jujutsu goes looking for the closest .jj/ directory in an ancestor of wherever you're currently standing (your current working directory). it's giving "mom, where's my repo".
• --ignore-working-copy — don't snapshot the working copy, and don't update it 🙈 by default, Jujutsu snapshots the working copy at the start of every command. and then at the end of the command it updates it again, but only if the command modified the working-copy commit (@). so if you wanna skip the snapshotting entirely and just look at a possibly stale working-copy commit, this is your girl. super useful in like a command prompt, especially if you've got another process out there committing the working copy. multitasking queen energy. also note: loading the repo at a specific operation with --at-operation implies --ignore-working-copy. they're a package deal. 💀
• --no-integrate-operation — run the command as usual but don't integrate any operations ⭐ when you pass this, the operations still get created like normal, they just don't get integrated into the operation log. and the working copy doesn't get updated either. the command will print the resulting operation ID. you can pass that ID to e.g. jj --at-op to peek at the resulting repo state, or 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. so many options, so much power.

careful, bestie: this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. 😭 the push is happening. it's 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. 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 there are 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. and --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. slay. 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 chaos energy, 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. it's the "no small talk" setting. warnings and errors will still be printed though. the important stuff always gets through. 💅
• --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 the string value isn't enclosed by any TOML constructs (such as array notation), quotes can be omitted. iykyk.
• --config-file <PATH> — additional configuration files (can be repeated) 💜

and that's the whole page, bestie!! you ate that. 🫶 this was the version release, sitting pretty in the jj-version(1) corner of the manual. now go check your version and feel iconic. 👑✨