jj-workspace-root(1)

📦 version 0.46.0, in alpine 3.24, arch rolling, nixos 26.05, nixpkgs unstable, ubuntu stonking

✨ jj-workspace-root(1) ✨

okay so bestie, this is jj-workspace-root from the General Commands Manual — the lil command that ~tells you where your workspace lives~. it's short, it's sweet, it's giving "one job and it does it flawlessly". 💅

🌸 NAME 🌸

jj-workspace-root</p> — show the workspace root directory. that's it. that's the whole personality. 👑

🦋 SYNOPSIS 🦋

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

💖 DESCRIPTION 💖

Show the workspace root directory.

literally just prints where your workspace root is at. no notes, iconic behaviour, periodt. ✨

🎀 OPTIONS 🎀

  • --name <NAME> — the name of the workspace you wanna peek at (defaults to the current one, obvi).
  • -h, --help — print the help. if you pass a lil -h instead, you get the summary version. your choice bestie 🫶

🌈 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 your current working directory. it's like a scavenger hunt but the prize is a repo. 🔍

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

normally, Jujutsu snapshots the working copy at the beginning of every single command. and then the working copy gets updated at the end of the command too, if the command modified the working-copy commit (@). but if you'd rather skip the snapshotting and just look at a possibly stale working-copy commit, this flag is your girl. super useful, like, in a command prompt — especially when you've got another process out there committing the working copy. 😭

ngl, loading the repo at a specific operation with --at-operation implies --ignore-working-copy. just so you know. 💀
  • --no-integrate-operation — run the command as usual but don't integrate any operations.

when you give this option, the operations still get created like normal, but they do not get integrated into the operation log. also the working copy won't be updated. 🙈

the command will print the resulting operation ID. you can pass that to, like, 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. so many options, so much power. 👑

✋ heads up: this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. no cap, it really will.
  • --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. got it? got it. 💅

  • --at-operation <AT_OPERATION> — the 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. you don't need the whole thing, bestie. 😌

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. you can, doesn't mean you should. 🍓

  • --debug — turn on debug logging. for when you're deep in the trenches. 🔥
  • --color <WHEN> — when to colorize the output.

possible values:

  • always
  • never
  • debug
  • auto
  • --quiet — silence non-primary command output.

like, 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" mode. 🤫

warnings and errors will still be printed though. those always get through. 😭

  • --no-pager — disable the pager. sometimes you just want your output to go straight to the terminal, no middleman. 💜
  • --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. fancy? a little. but you got this. 🧚

  • --config-file <PATH> — additional configuration files (can be repeated). stack 'em up bestie, it's giving layers. 🌸

and that's the whole page, my love ✨</p> jj-workspace-root(1) comes to you from the source root, living it up under the General Commands Manual. mwah, go find your workspace root. 💖🦋🎀

📦 where this page comes from