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 remote
27 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 are
33 offline. There is no guarantee that locks on the server have not
34 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 can
39 be updated for the next push. All other locks are held by someone
40 else. Contrary to --local, this option will also detect locks which
41 are held by us despite no local lock information being available
42 (e.g. because the file had been locked from a different clone); it
43 will also detect 'broken' locks (e.g. if someone else has
44 forcefully unlocked our files).
45
46 -l <num>, --limit=<num>
47 Specifies number of results to return.
48
49 --json
50 Writes lock info as JSON to STDOUT if the command exits
51 successfully. Intended for interoperation with external tools. If
52 the command returns with a non-zero exit code, plain text messages
53 will be sent to STDERR.
54
56 git-lfs-lock(1), git-lfs-unlock(1).
57
58 Part of the git-lfs(1) suite.
59
60
61
62 GIT-LFS-LOCKS(1)