jj(1)

📦
version 0.46.0 · 4 versions
, in arch rolling, nixpkgs unstable

🦋 jj(1): the Jujutsu manual, bestie edition 🦋

okay so welcome to jj(1), the manual page for Jujutsu, aka An experimental VCS 💅 yes, the manpage itself says experimental, so we're keeping that energy fr fr.

✨ NAME ✨

jj — Jujutsu (An experimental VCS) 🫶

🌸 SYNOPSIS 🌸

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

🎀 DESCRIPTION 🎀

Jujutsu (An experimental VCS) 💖

To get started, see the tutorial at jj help -k tutorial — the link is https://docs.jj-vcs.dev/latest/tutorial/ ✨

💅 OPTIONS 💅

  • -h, --help — print help (see a summary with -h) 👑
  • -V, --version — print version 🏷️

🌈 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. 💀

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

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

  • --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) 📁

👑 SUBCOMMANDS 👑

  • jj-abandon(1) — abandon a revision 🗑️
  • jj-absorb(1) — move changes from a revision into the stack of mutable revisions 🧽
  • jj-arrange(1) — interactively arrange the commit graph 🧩
  • jj-bisect(1) — find a bad revision by bisection 🔍
  • jj-bookmark(1) — manage bookmarks [default alias: b] 🔖
  • jj-commit(1) — update the description and create a new change on top [default alias: ci] 📝
  • jj-config(1) — manage config options ⚙️
  • jj-converge(1) — converge divergent changes 🌀
  • jj-describe(1) — update the change description or other metadata [default alias: desc] 🏷️
  • jj-diff(1) — compare file contents between two revisions 🆚
  • jj-diffedit(1) — touch up the content changes in a revision with a diff editor ✏️
  • jj-duplicate(1) — create new changes with the same content as existing ones 👯
  • jj-edit(1) — sets the specified revision as the working-copy revision 🛠️
  • jj-evolog(1) — show how a change has evolved over time 📜
  • jj-file(1) — file operations 📂
  • jj-fix(1) — update files with formatting fixes or other changes 🪄
  • jj-gerrit(1) — interact with Gerrit Code Review 🐧
  • jj-git(1) — commands for working with Git remotes and the underlying Git repo 🌐
  • jj-help(1) — print this message or the help of the given subcommand(s) ❓
  • jj-interdiff(1) — show differences between the diffs of two revisions 🔄
  • jj-log(1) — show revision history 📚
  • jj-metaedit(1) — modify the metadata of a revision without changing its content 🏷️
  • jj-new(1) — create a new, empty change and (by default) edit it in the working copy 🆕
  • jj-next(1) — move the working-copy commit to the child revision ⏭️
  • jj-operation(1) — commands for working with the operation log 🗃️
  • jj-parallelize(1) — parallelize revisions by making them siblings 🧬
  • jj-prev(1) — change the working copy revision relative to the parent revision ⏮️
  • jj-rebase(1) — move revisions to different parent(s) 🌱
  • jj-redo(1) — redo the most recently undone operation 🔁
  • jj-resolve(1) — resolve conflicted files with an external merge tool 🧰
  • jj-restore(1) — restore paths from another revision ♻️
  • jj-revert(1) — apply the reverse of the given revision(s) ↩️
  • jj-root(1) — show the current workspace root directory (shortcut for jj workspace root) 🏠
  • jj-run(1) — run a command across a set of revisions. 🏃‍♀️
  • jj-show(1) — show revision metadata and diff 👀
  • jj-sign(1) — cryptographically sign a revision ✍️
  • jj-simplify-parents(1) — simplify parent edges for the specified revision(s) 🪢
  • jj-sparse(1) — manage which paths from the working-copy commit are present in the working copy 🧺
  • jj-split(1) — split a revision in two ✂️
  • jj-squash(1) — move changes from a revision into another revision 🥞
  • jj-status(1) — show high-level repo status [default alias: st] 📊
  • jj-tag(1) — manage tags 🏷️
  • jj-undo(1) — undo the last operation ⏪
  • jj-unsign(1) — drop a cryptographic signature 🗑️
  • jj-util(1) — infrequently used commands such as for generating shell completions 🧰
  • jj-version(1) — display version information 🏷️
  • jj-workspace(1) — commands for working with workspaces 🏢

🧚 EXTRA 🧚

jj help --help lists available keywords. Use jj help -k to show help for one of these keywords. 💡

⭐ VERSION ⭐

v0.46.0 — periodt 💅

signed off from the <hotpink>jj 0.46.0</hotpink> manual / version v0.46.0, source-version jj 0.46.0 — the footer doesn't list a date, so consider this your cute timestamp, bestie 🫶🎀

📦 where this page comes from