Unlock a Git Worktree
Unlocking a worktree lifts administrative protection, restoring maintenance actions including renaming, relocating, deleting, and pruning.
When to Unlock a Worktree
Unlock a worktree when its protection period has concluded:
- A long-running build, benchmark, or continuous integration run has finished.
- A release candidate branch has been merged into main or signed off by QA.
- You are ready to clean up disk space by deleting or pruning the worktree.
- You need to rename the worktree or relocate its directory path.
How to Unlock a Worktree
- In the Worktrees panel, locate the locked worktree (indicated by a Lock icon 🔒).
- Select the three-dot Actions menu beside the worktree.
- Select Unlock.

WorktreeWise communicates with Git to remove the lock metadata. A confirmation notification confirms the lock removal.

What Happens After Unlocking
- Lock Metadata Cleared: The recorded lock reason and Git lockfile (
.git/worktrees/<name>/locked) are removed. - Operations Restored: The Delete, Rename, and Change Folder (Move) options in the Actions menu are immediately re-enabled.
- Zero File Impact: Unlocking does not touch project files, uncommitted edits, or local branch commit history.
- Prune Eligibility: If the worktree directory is later removed from disk, Git and WorktreeWise will recognize it as an eligible candidate for pruning.
Related Pages
- Lock a Git Worktree: Learn how and when to protect critical worktrees.
- Delete a Git Worktree: Remove unlocked worktrees safely.
- Prune Damaged Worktrees: Clean up stale metadata after directories are deleted.