Skip to content

Commit

Permalink
docs: explain that we don't support shallow clones (#675)
Browse files Browse the repository at this point in the history
  • Loading branch information
martinvonz committed Oct 27, 2022
1 parent 59717aa commit 423ebb1
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/git-compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,9 @@ a comparison with Git, including how workflows are different, see the
* **Submodules: No.** They will not show up in the working copy, but they will
not be lost either.
* **Partial clones: No.** We use the [libgit2](https://libgit2.org/) library,
which doesn't have support for partial clones.
which [doesn't have support for partial clones](https://github.com/libgit2/libgit2/issues/5564).
* **Shallow clones: No.** We use the [libgit2](https://libgit2.org/) library,
which [doesn't have support for shallow clones](https://github.com/libgit2/libgit2/issues/3058).
* **git-worktree: No.** However, there's native support for multiple working
copies backed by a single repo. See the `jj workspace` family of commands.
* **Sparse checkouts: No.** However, there's native support for sparse
Expand Down

0 comments on commit 423ebb1

Please sign in to comment.