jj-git-clone(1)

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

💅 NAME 💅

  • jj-git-clone — create a new repo backed by a clone of a Git repo.

okay so bestie, welcome to jj-git-clone(1) from the General Commands Manual — this is the whole “clone a Git repo into a fresh jj repo” moment, and it’s lowkey iconic. 💖✨

✨ SYNOPSIS ✨

jj git clone [-R|--repository] [--remote] [--colocate]
[--ignore-working-copy] [--no-colocate] [--no-integrate-operation]
[--depth] [--ignore-immutable] [--at-operation] [-b|--branch] [--debug]
[-t|--tag] [--color] [--object-hash] [--quiet] [--no-pager] [--config]
[--config-file] [-h|--help] <SOURCE> [DESTINATION]

🌸 DESCRIPTION 🌸

Create a new repo backed by a clone of a Git repo. That’s the vibe: you point at a Git repo, and jj makes you a new repo backed by a clone of it. slay. 🌈

🎀 OPTIONS 🎀

  • --remote <REMOTE_NAME> [default: origin] — name of the newly created remote. 💅
  • --colocate — colocate the Jujutsu repo with the git repo. This specifies that the jj repo should also be a valid git repo, so you can use both jj and git commands in the same directory. The repository will contain a .git dir in the top-level, and regular Git tools will be able to operate on the repo. This is the default, and this option has no effect unless the [git.colocate config] is set to false.
  • --no-colocate — disable colocation of the Jujutsu repo with the git repo. This prevents Git tools that are unaware of jj and regular Git commands from operating on the repo. The Git repository that stores most of the repo data will be hidden inside a sub-directory of the .jj directory. See [colocation docs] for some minor advantages of non-colocated workspaces.
  • --depth <DEPTH> — create a shallow clone of the given depth. 🫶
  • -b, --branch <BRANCH> — name of the branch to fetch and use as the parent of the working-copy change (can be repeated). If not present, all branches are fetched and the repository’s default branch is used as parent of the working-copy change. By default, the specified pattern matches branch names with glob syntax, but only * is expanded. Other wildcard characters such as ? are not supported. Patterns can be repeated or combined with [logical operators] to specify multiple branches, but only union and negative intersection are supported. If there are multiple matching branches, the first exact branch name is used as the working-copy parent. Examples: push-*, (push-* | foo/*) ~ foo/unwanted.
  • -t, --tag <TAG> — fetch only some of the tags (can be repeated). By default, the specified pattern matches tag names with glob syntax, but only * is expanded. Other wildcard characters such as ? are not supported. Patterns can be repeated or combined with [logical operators] to specify multiple tags, but only union and negative intersection are supported.
  • --object-hash <OBJECT_HASH> — object hash algorithm for the local Git repository. Must match the remote’s hash algorithm, otherwise the operation will fail. Most existing repositories today still use the classic SHA-1 format, which is also the default if not configured otherwise by the [git.object-hash config]. See also Git’s [hash-function-transition] document for an in-depth explanation of the migration towards stronger hash functions. Possible values:
  • -h, --help — print help (see a summary with -h). 🎀
  • <SOURCE> — URL or path of the Git repo to clone. Local path will be resolved to absolute form. 🌸
  • [DESTINATION] — specifies the target directory for the Jujutsu repository clone. If not provided, defaults to a directory named after the last component of the source URL. The full directory path will be created if it doesn’t exist. ✨

🦋 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). 💜

xoxo bestie 💖 — source/version: clone · manual: jj-git-clone(1) · date: not printed in the original footer, so no cap, just vibes 🎀✨

📦 where this page comes from