Release a worktree
A slot stays held by its task or person until the task is completed, deleted or reset, or the slot is released. When a hold is no longer needed, release the slot so the next task can use it. Releasing keeps the worktree and its uncommitted work, and it doesn't complete or delete the task that held it.
Who can do this: releasing needs the permission to edit worktrees. A greyed-out Release tells you why when you hover it.
Release slots
- In the sidebar, select Directory, then the Worktrees tab.
- Find the slots: in Filter & view, set Occupancy to Held by a task or Held by a person.
- Tick the checkbox at the end of each slot's row. A bar appears above the list.
- Select Release in the bar. If it isn't shown, open the bar's ⋯ menu.
- Read the confirmation: it names the slots it will release.
- Confirm.
A line under the bar says how many slots were released, and why any slot was refused.
Other actions in the same bar
| Action | When to use it |
|---|---|
| Stop stack | A slot's app stack is up but nothing uses it. Its data and the worktree are kept. |
| Sync Git | A slot is behind its base branch and has no uncommitted work. |
| Delete | The slot should go for good. It deletes the worktree and can't be undone. Requires the org admin role. |
Select ✕ to clear the selection.
Related
- Check a slot before releasing it: Read a worktree's status.
- To stop the task itself instead: Stop, restart or reset a task.
- Every action in the bar: Worktrees.
- When a hold ends on its own: How worktrees work.