Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help

       git-lfs-locks - Lists currently locked files from the Git LFS server.

       git lfs locks options

       Lists current locks from	the Git	LFS server.

       -r name --remote=name
	      Specify the Git LFS server to use. Ignored if the	lfs.url	config
	      key is set.

       -i <id> --id=<id>
	      Specifies	a lock by its ID. Returns a single result.

       -p <path> --path=<path>
	      Specifies	a lock by its path. Returns a single result.

	      Lists only our own locks which are cached	locally. Skips	a  re-
	      mote call.

	      Lists  cached locks from the last	remote call. Contrary to --lo-
	      cal, this	will include locks of other users as well. This	option
	      is intended to display the last known locks in case you are off-
	      line. There is no	guarantee that locks on	the  server  have  not
	      changed in the meanwhile.

	      Verifies the lock	owner on the server and	marks our own locks by
	      'O'. Own locks are actually held by us and  corresponding	 files
	      can  be  updated	for the	next push. All other locks are held by
	      someone else. Contrary to	--local, this option will also	detect
	      locks which are held by us despite no local lock information be-
	      ing available (e.g. because the file had been locked from	a dif-
	      ferent clone); it	will also detect 'broken' locks	(e.g. if some-
	      one else has forcefully unlocked our files).

       -l <num>	--limit=<num>
	      Specifies	number of results to return.

       --json Writes lock info as JSON to STDOUT if the	command	exits success-
	      fully.  Intended	for interoperation with	external tools.	If the
	      command returns with a non-zero exit code, plain	text  messages
	      will be sent to STDERR.

       git-lfs-lock(1),	git-lfs-unlock(1).

       Part of the git-lfs(1) suite.

				   May 2020		      GIT-LFS-LOCKS(1)


Want to link to this manual page? Use this URL:

home | help