jj-git-colocation-status(1)

💖 jj-git-colocation-status(1) 💖

okay bestie, welcome to the manual page for jj-git-colocation-status(1) — she's a general commands manual gal and she is so ready to spill the tea on your repo's colocation sitch. 🫶

---

✨ NAME ✨

jj-git-colocation-status — show the current colocation status 👑

🦋 SYNOPSIS 🦋

jj git colocation status [-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 current colocation status ✨ like that's literally it, that's the whole vibe, no cap.

💅 OPTIONS 💅

• -h, --help — print help, but the sparknotes version if you use the short -h 🎀

🌈 GLOBAL OPTIONS 🌈

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

fr fr, by default Jujutsu goes hunting for the closest .jj/ directory in an ancestor of wherever you're currently working from. she finds it herself, she's an independent queen 💁♀️

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

okay so by default, Jujutsu snapshots the working copy at the beginning of every command. iconic behavior. the working copy also gets updated at the end of the command, if the command modified the working-copy commit (@). but if you wanna avoid snapshotting the working copy and instead see a possibly stale working-copy commit, 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. very specific bestie energy, we love to see it.

jsyk: loading the repository at a specific operation with --at-operation implies --ignore-working-copy. the way that implication just happens... periodt.

• --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. lowkey a whole thing.

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. so many options bestie, so many doors 🚪

note that this does not prevent side effects outside the repo. for example, jj git push --no-integrate-operation will still perform the push. 😭 she's not protecting you from that one.

• --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. main character energy: rules are for other people.

heads up though — this option only affects the check. it does not affect the immutable_heads() revset or the immutable template keyword. those stay exactly as they were, no notes 💅

• --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. time travel but make it version control 🕰️✨

use jj op log to find the operation ID you want. any unambiguous prefix of the operation ID is enough. no need for the whole thing, she'll know what you mean 🧚

when loading the repo at an earlier operation, the working copy will be ignored, as if --ignore-working-copy had been specified. yeah. it just does that.

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. chaotic, but legal 💀

• --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. she's being mysterious on purpose.

warnings and errors will still be printed. those always get to speak 🗣️

• --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. so forgiving of her 🥰

• --config-file <PATH> — additional configuration files (can be repeated) 📚

---

and that's the whole page bestie, you ate that 🍓💜

this cute lil manual says status on the jj-git-colocation-status(1) footer, so consider this your official sign-off — mwah, go check that colocation status, ily 🎀✨