1GIT-LFS-CHECKOUT(1) GIT-LFS-CHECKOUT(1)
2
3
4
6 git-lfs-checkout - Update working copy with file content if available
7
9 git lfs checkout filespec... git lfs checkout --to path { --ours |
10 --theirs | --base } file...
11
13 Try to ensure that the working copy contains file content for Git LFS
14 objects for the current ref, if the object data is available. Does not
15 download any content, see git-lfs-fetch(1) for that.
16
17 Checkout scans the current ref for all LFS objects that would be
18 required, then where a file is either missing in the working copy, or
19 contains placeholder pointer content with the same SHA, the real file
20 content is written, provided we have it in the local store. Modified
21 files are never overwritten.
22
23 Filespecs can be provided as arguments to restrict the files which are
24 updated.
25
26 When used with --to and the working tree is in a conflicted state due
27 to a merge, this option checks out one of the three stages of the con‐
28 flict into a separate file. This can make using diff tools to inspect
29 and resolve merges easier.
30
32 --base Check out the merge base of the specified file.
33
34 --ours Check out our side (that of the current branch) of the conflict
35 for the specified file.
36
37 --theirs
38 Check out their side (that of the other branch) of the conflict
39 for the specified file.
40
41 --to path
42 If the working tree is in a conflicted state, check out the por‐
43 tion of the conflict specified by --base, --ours, or --theirs to
44 the given path.
45
47 · Checkout all files that are missing or placeholders
48
49 git lfs checkout
50
51 · Checkout a specific couple of files
52
53 git lfs checkout path/to/file1.png path/to.file2.png
54
55
56
58 git-lfs-fetch(1), git-lfs-pull(1).
59
60 Part of the git-lfs(1) suite.
61
62
63
64 April 2019 GIT-LFS-CHECKOUT(1)