1GIT-LFS-CLONE(1)                                              GIT-LFS-CLONE(1)
2
3
4

NAME

6       git-lfs-clone - Efficiently clone a LFS-enabled repository
7

SYNOPSIS

9       git lfs clone [git clone options] <repository> [<directory>]
10

DESCRIPTION

12       Clone an LFS enabled Git repository more efficiently by disabling LFS
13       during the git clone, then performing a 'git lfs pull' directly
14       afterwards.
15
16       'git lfs clone' also installs all of the repo-level hooks (.git/hooks)
17       that LFS requires to operate. If --separate-git-dir is given, the hooks
18       will be installed there.
19
20       This is faster than a regular 'git clone' because that will download
21       LFS content using the smudge filter, which is executed individually per
22       file in the working copy. This is relatively inefficient compared to
23       the batch mode and parallel downloads performed by 'git lfs pull'.
24

OPTIONS

26       All options supported by 'git clone'
27
28       -I <paths>, --include=<paths>
29           See INCLUDE AND EXCLUDE.
30
31       -X <paths>, --exclude=<paths>
32           See INCLUDE AND EXCLUDE.
33
34       --skip-repo
35           Skip installing repo-level hooks (.git/hooks) that LFS requires.
36           Disabled by default.
37

INCLUDE AND EXCLUDE

39       You can configure Git LFS to only fetch objects to satisfy references
40       in certain paths of the repo, and/or to exclude certain paths of the
41       repo, to reduce the time you spend downloading things you do not use.
42
43       In your Git configuration or in a .lfsconfig file, you may set either
44       or both of lfs.fetchinclude and lfs.fetchexclude to comma-separated
45       lists of paths. If lfs.fetchinclude is defined, Git LFS objects will
46       only be fetched if their path matches one in that list, and if
47       lfs.fetchexclude is defined, Git LFS objects will only be fetched if
48       their path does not match one in that list. Paths are matched using
49       wildcard matching as per gitignore(5).
50
51       Note that using the command-line options -I and -X override the
52       respective configuration settings. Setting either option to an empty
53       string clears the value.
54

SEE ALSO

56       git-clone(1), git-lfs-pull(1), gitignore(5).
57
58       Part of the git-lfs(1) suite.
59
60
61
62                                                              GIT-LFS-CLONE(1)
Impressum