GIT-LFS-UNLOCK(1)

💖 GIT-LFS-UNLOCK(1) — git-lfs-unlock 💖

okay bestie, welcome to the GIT-LFS-UNLOCK(1) page for git-lfs-unlock — literally the glow-up that removes a file’s “locked” era on the Git LFS server. let’s go 🫶✨

---

🌸 NAME 🌸

git-lfs-unlock — Remove "locked" setting for a file on the Git LFS server 💅

---

🦋 SYNOPSIS 🦋

git lfs unlock [<options>] <path>

---

✨ DESCRIPTION ✨

So here’s the vibe: this removes the given file path as "locked" on the Git LFS server. no cap.

But bestie, there are rules: files must exist and have a clean git status before they can be unlocked. the --force flag will skip these checks 💀

lowkey important: --force is the skip-the-checks button, exactly like the description says. it’s giving power, so use it with intent ✨

---

🎀 OPTIONS 🎀

• -r <name>, --remote=<name> — Specify the Git LFS server to use. Ignored if the lfs.url config key is set. iykyk, config wins 💅
• -f, --force — Tells the server to remove the lock, even if it’s owned by another user. this is the “skip those checks” energy from above 🔥
• -i <id>, --id=<id> — Specifies a lock by its ID instead of path. lock ID main character moment 🎀
• -j, --json — Writes lock info as JSON to STDOUT if the command exits successfully. Intended for interoperation with external tools. If the command returns with a non-zero exit code, plain text messages will be sent to STDERR. tool-friendly and honest about errors ✨

---

🌈 SEE ALSO 🌈

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

Part of the git-lfs(1) suite. the whole fam is here 🫶

---

okay bestie, that’s the whole GIT-LFS-UNLOCK(1) page 💅 — the footer was just the page label GIT-LFS-UNLOCK(1), and there was no source/version or date line in the original, so I’m not making one up 🫶✨