Release a lock
Releasing a lock gives up your check-out without publishing. Use it when you checked out
a file but decided not to keep your changes, or locked something by mistake.
Prerequisites
- You hold the lock (Locked by Me) on the file.
Steps
- In the Files tab, right-click the file → Release (release lock).
- If you have unpublished local versions on that file, GitM warns you that releasing will
discard them, because they were never published. Confirm only if you're sure.
Expected result
- The lock is released; the file returns to Not Locked and read-only.
- Any unsaved working-tree changes and unpublished local versions for that file are
discarded.
Release vs. Check In
| You want to… |
Use |
| Keep and publish your changes |
Check In |
| Keep a local checkpoint, keep editing |
Save Local Version |
| Give up your changes and unlock |
Release (this page) |
Troubleshooting
| Symptom |
Cause |
Fix |
| Warning about discarding "N unpublished local versions" |
You have Save Local Version checkpoints not yet checked in. |
Cancel and check in if you want to keep them. |
| "You're offline — Release Lock needs a connection" |
The lock lives on the server, so it can't be released offline. |
Reconnect, then release. See Work offline. |
| Release fails |
Couldn't reach the LFS lock server. |
Check your connection; retry. |
| The warning appears even though you just checked in |
Was a stale-count bug (fixed). |
Refresh the task pane; the file should show no local versions. |
Known limitations
- Releasing is destructive to unpublished work by design — it reverts the file to its
last published state. There's no undo.
- If a teammate is unreachable and holding a lock, you can't release it yourself; an admin
must force-unlock.