GIT-LFS-LOCKS(1)

💅 GIT-LFS-LOCKS(1) — like, the locks one 💖

okay so bestie, welcome to git-lfs-locks — the page for the git lfs locks command, aka your personal window into every single file that somebody's got locked on the Git LFS server 🔒✨ no cap it's genuinely useful.

---

✨ SYNOPSIS ✨

git lfs locks [options]

that's it. that's the whole vibe. one command, a pile of options, let's go 🎀

---

🦋 DESCRIPTION 🦋

it lists the current locks from the Git LFS server. that's the whole assignment 💅 like, you run it and it tells you what's locked right now. iconic behaviour honestly.

---

🎀 OPTIONS 🎀 (the good part, fr fr)

• -r <name>, --remote=<name> — picks which Git LFS server you're talking to. heads up bestie: this gets ignored if the lfs.url config key is set. so if you're sitting there going "why is my remote flag doing nothing 😭" — check your config, that's the culprit.
• -i <id>, --id=<id> — grabs a lock by its ID. returns a single result. one lock, one answer, no scrolling 🫶
• -p <path>, --path=<path> — grabs a lock by its path instead. also returns a single result. pick your fighter: ID or path, either works 💜
• --local — lists only our own locks that are cached locally, and skips the remote call entirely. offline? unbothered? this one's for you ⭐
• --cached — lists cached locks from the last remote call. and contrary to --local, this one does include other users' locks too 🌈 so it's the full picture from last time you checked. it's intended for showing you the last known locks when you're offline, but — and this is the important bit — there is no guarantee that locks on the server have not changed in the meanwhile. so don't treat it like gospel, ngl 💀
• --verify — verifies the lock owner on the server and marks our own locks with 'O' 🔥 own locks are actually held by us, and the corresponding files can be updated for the next push. all other locks are held by someone else. and here's where it eats: contrary to --local, this option will also detect locks that are held by us even when there's no local lock information available (say, because the file was locked from a different clone 👀). it'll also detect 'broken' locks — for example, if someone else has forcefully unlocked our files. yeah. messy. but at least now you know 💅
• -l <num>, --limit=<num> — specifies how many results to return. keep it snappy 🌸
• -j, --json — writes lock info as JSON to STDOUT if the command exits successfully. this one's intended for interop with external tools, iykyk 🧚 but listen: if the command returns a non-zero exit code, then plain text messages get sent to STDERR instead. so don't pipe it blindly and then act surprised, ok? 🙈

---

👑 SEE ALSO 👑

• git-lfs-lock(1)
• git-lfs-unlock(1)

and it's all part of the git-lfs(1) suite, obviously 💖

---

that's the whole page bestie, go lock some files responsibly 🦋✨

— signed off from the GIT-LFS-LOCKS(1) page itself, matching footer and all, mwah 💋