jj(1) General Commands Manual jj(1)

jj - Jujutsu (An experimental VCS)

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

Jujutsu (An experimental VCS)

To get started, see the tutorial at https://jj-vcs.github.io/jj/latest/tutorial/.

Path to repository to operate on

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

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

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.

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.

Enable debug logging
When to colorize output (always, never, debug, auto)
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.

Disable the pager
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 doesn't contain any TOML constructs (such as array notation), quotes can be omitted.

Additional configuration files (can be repeated)
Print help (see a summary with '-h')
Print version

Abandon a revision
Move changes from a revision into the stack of mutable revisions
Apply the reverse of a revision on top of another revision
Manage bookmarks [default alias: b]
Update the description and create a new change on top
Manage config options
Update the change description or other metadata
Compare file contents between two revisions
Touch up the content changes in a revision with a diff editor
Create new changes with the same content as existing ones
Sets the specified revision as the working-copy revision
Show how a change has evolved over time
File operations
Update files with formatting fixes or other changes
Commands for working with Git remotes and the underlying Git repo
Print this message or the help of the given subcommand(s)
Create a new repo in the given directory
Compare the changes of two commits
Show revision history
Create a new, empty change and (by default) edit it in the working copy
Move the working-copy commit to the child revision
Commands for working with the operation log
Parallelize revisions by making them siblings
Change the working copy revision relative to the parent revision
Move revisions to different parent(s)
Resolve a conflicted file with an external merge tool
Restore paths from another revision
Show the current workspace root directory
Show commit description and changes in a revision
Simplify parent edges for the specified revision(s)
Manage which paths from the working-copy commit are present in the working copy
Split a revision in two
Move changes from a revision into another revision
Show high-level repo status
Manage tags
Infrequently used commands such as for generating shell completions
Undo an operation (shortcut for `jj op undo`)
Display version information
Commands for working with workspaces

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

v0.25.0

jj 0.25.0