jj-parallelize(1)

okay so you pulled up jj-parallelize(1), from the General Commands Manual, and honestly? taste. 💅 let's get into it, bestie.

🎀 NAME 🎀

jj-parallelize — parallelize revisions by making them siblings ✨

📜 SYNOPSIS 📜

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

🦋 DESCRIPTION 🦋

so. the whole vibe of this command is: it parallelizes revisions by making them siblings. that's it, that's the fantasy. 🫶

run jj parallelize 1::2 and the history does this little glow-up:

3            3
|           / \
2    ->    1   2
|           \ /
1            0
|
0

what the command is actually saying, in girl terms, is "these revisions are, like, independent actually" — like they should no longer be ancestors/descendants of each other. periodt. 😌

BUT. and this is the important part, don't skip it:

• revisions outside the set that were previously ancestors of a revision in the set? they remain ancestors of it. for example, revision 0 above remains an ancestor of both 1 and 2. 🧚
• revisions outside the set that were previously descendants of a revision in the set? they remain descendants of it. for example, revision 3 above remains a descendant of both 1 and 2. 💫

so therefore, jj parallelize '1 | 3' is a no-op. and the reason is lowkey iconic: 2, which is not in the target set, was a descendant of 1 before, so it stays a descendant; and it was an ancestor of 3 before, so it stays an ancestor. the vibes are conserved. that's just science. 🔬

🔥 OPTIONS 🔥

• -h, --help — print help (see a summary with -h)
• [REVSETS] — the revisions to parallelize (aliases: -r)

🌈 GLOBAL OPTIONS 🌈

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

by default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory. 🔍

• --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. the working copy is also updated at the end of the command, if the command modified the working-copy commit (@). if you want to 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. 🙈

• --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 don't be shocked when the push actually happens, bestie.

• --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.

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. so yes, you can, no, you probably shouldn't. 🕰️

• --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. (yes bestie, the scary stuff still comes 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 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. 🌸 this one's sourced from parallelize, and you found it sitting pretty under jj-parallelize(1) 🎀 no cap, go make some siblings out of your history. 💖