jj-git-clone(1)

NAME
jj-git-clone - Create a new repo backed by a clone of a Git repo

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

DESCRIPTION
Create a new repo backed by a clone of a Git repo

OPTIONS

--remote <REMOTE_NAME> [default: origin]
    Name of the newly created remote

--colocate
    Colocate the Jujutsu repo with the git repo Specifies that the `jj` repo should also be a valid `git` repo, allowing the use of both `jj` and `git` commands in the same directory. The repository will contain a `.git` dir in the top-level. 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`. [git.colocate config]: https://docs.jj-vcs.dev/latest/config/#default-colocation

--no-colocate
    Disable colocation of the Jujutsu repo with the git repo Prevent 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. [colocation docs]: https://docs.jj-vcs.dev/latest/git-compatibility/#colocated-jujutsugit-repos

--depth <DEPTH>
    Create a shallow clone of the given depth

--fetch-tags <FETCH_TAGS>
    Configure when to fetch tags Unless otherwise specified, the initial clone will fetch all tags, while all subsequent fetches will only fetch included tags.
    Possible values:

    •   all: Always fetch all tags

    •   included: Only fetch tags that point to objects that are already being transmitted

    •   none: Do not fetch any tags

-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` [logical operators]: https://docs.jj-vcs.dev/latest/revsets/#string-patterns

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

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