jj-duplicate(1)

🌸 jj-duplicate(1) 🌸

okay bestie, sit DOWN, because jj-duplicate is about to become your new fave. it's a General Commands Manual page, it's giving very much "clone but make it a change", and yes, I'm gonna walk you through every last flag. no skipping, no skimming, periodt. 💅

---

✨ NAME ✨

jj-duplicate — create new changes with the same content as existing ones 🫶

---

🦋 SYNOPSIS 🦋

jj duplicate [-R|--repository] [--ignore-working-copy] [-o|--onto]
[-A|--insert-after] [--no-integrate-operation] [-B|--insert-before]
[--ignore-immutable] [--at-operation] [--debug] [--color] [--quiet]
[--no-pager] [--config] [--config-file] [-h|--help] [REVSETS]

---

💖 DESCRIPTION 💖

Create new changes with the same content as existing ones. literally copy-paste energy, but for commits. 💅

Okay so here's the tea on how it decides where the new copies go:

• When none of the --onto, --insert-after, or --insert-before arguments are provided, commits will be duplicated onto their existing parents or onto other newly duplicated commits. so they just kinda... land where they already were. cozy. 🛋️
• When any of the --onto, --insert-after, or --insert-before arguments are provided, the roots of the specified commits will be duplicated onto the destination indicated by the arguments. Other specified commits will be duplicated onto these newly duplicated commits. If the --insert-after or --insert-before arguments are provided, the new children indicated by the arguments will be rebased onto the heads of the specified commits. 😤 do you see the vision. it's a whole choreography.

By default, the duplicated commits retain the descriptions of the originals. ✨ but guess what — you can customize that with the templates.duplicate_description setting. your duplicates, your narrative, your rules. 👑

---

🎀 OPTIONS 🎀

• -o, --onto <REVSETS> — The revision(s) to duplicate onto (can be repeated to create a merge commit). repeat it and suddenly it's a merge commit, no cap. 🌈
• -A, --insert-after <REVSETS> — The revision(s) to insert after (can be repeated to create a merge commit). stack 'em up, bestie. 🧚
• -B, --insert-before <REVSETS> — The revision(s) to insert before (can be repeated to create a merge commit). same deal, opposite direction. 💫
• -h, --help — Print help (see a summary with '-h'). the short version exists, if you're in a rush. 🏃‍♀️
• [REVSETS] — The revision(s) to duplicate (default: @) [aliases: -r]. yes the default is @, so if you give it nothing it duplicates your current working-copy commit. iconic behaviour honestly. 🌟

---

👑 GLOBAL OPTIONS 👑

these are the big-picture, whole-toolkit vibes. they work everywhere, not just here. 💜

• -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. it's out here doing a little scavenger hunt for you, so sweet. 🔍

• --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. so like, that one's automatic, you don't gotta ask.

• --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. the push is pushing, bestie. nothing can stop it.

• --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. so it's a vibe check bypass, not a rules-rewrite. 🙈

• --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. time travel but it's commits and also it's slightly chaotic. 🕰️

• --debug — Enable debug logging. for when you simply must know everything. 🔬
• --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 "k, thanks, that's all I needed" mode. 🤫

Warnings and errors will still be printed. those ones do not get the silent treatment, bestie.

• --no-pager — Disable the pager. output straight to your 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 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). stack those config files like an outfit. 🎀

---

and that's the whole page, bestie!! every option, every caveat, every little detail — we did not leave a single one behind, not on my watch. 💜

this was jj-duplicate from the General Commands Manual (section 1, obvi), a.k.a. jj-duplicate(1) — go forth and duplicate responsibly, and remember: repeat the revision flags to make a merge commit. slay. 💅🎀✨🦋👑