1GIT-LFS-LOCKS(1) GIT-LFS-LOCKS(1)
2
3
4
6 git-lfs-locks - Lists currently locked files from the Git LFS server.
7
9 git lfs locks options
10
12 Lists current locks from the Git LFS server.
13
15 -r name --remote=name
16 Specify the Git LFS server to use. Ignored if the lfs.url config
17 key is set.
18
19 -i <id> --id=<id>
20 Specifies a lock by its ID. Returns a single result.
21
22 -p <path> --path=<path>
23 Specifies a lock by its path. Returns a single result.
24
25 --local
26 Lists only our own locks which are cached locally. Skips a
27 remote call.
28
29 --cached
30 Lists cached locks from the last remote call. Contrary to
31 --local, this will include locks of other users as well. This
32 option is intended to display the last known locks in case you
33 are offline. There is no guarantee that locks on the server have
34 not changed in the meanwhile.
35
36 --verify
37 Verifies the lock owner on the server and marks our own locks by
38 ´O´. Own locks are actually held by us and corresponding files
39 can be updated for the next push. All other locks are held by
40 someone else. Contrary to --local, this option will also detect
41 locks which are held by us despite no local lock information
42 being available (e.g. because the file had been locked from a
43 different clone); it will also detect ´broken´ locks (e.g. if
44 someone else has forcefully unlocked our files).
45
46 -l <num> --limit=<num>
47 Specifies number of results to return.
48
49 --json Writes lock info as JSON to STDOUT if the command exits success‐
50 fully. Intended for interoperation with external tools. If the
51 command returns with a non-zero exit code, plain text messages
52 will be sent to STDERR.
53
55 git-lfs-lock(1), git-lfs-unlock(1).
56
57 Part of the git-lfs(1) suite.
58
59
60
61 July 2019 GIT-LFS-LOCKS(1)