Review cleanup

Review merged and pushed work before removal, and handle missing worktrees without deleting local work.

Review a suggestion

push& (Pushand) suggests cleanup for local branches and worktrees whose commits have been pushed and merged into the remote’s default branch. Suggestions are available with Pro, Unlimited, Beta and the Unlimited trial.

Before confirming, check the repository, branch, folder and any listed files. Read the commits and changed files if you are unsure what the branch contains. Cleanup checks the remote again before removal; an old suggestion is not permission to remove changed work.

Unmerged or unpushed work is not eligible for this cleanup. The main worktree, the default branch and branches without a tracked remote branch are excluded.

Understand what removal does

For a worktree, cleanup removes the working folder and its local branch. For an eligible branch without a working folder, it removes the local branch. It does not delete the remote branch.

Removing a worktree with changes is off by default. If you enable that option, review the displayed file list and type the repository name: those uncommitted and ignored files will be lost. Cancel if you need to keep anything. Turning the setting off afterwards does not restore deleted files.

If a preview changes, cleanup refuses removal. Review the new state before trying again; do not treat an earlier confirmation as approval of new changes.

Choose manual or automatic cleanup

In Settings, use Safety to leave cleanup on suggestions, turn it off, or enable automatic cleanup. Global defaults can be overridden for a repository.

Automatic cleanup only handles clean, pushed and merged work, never discards uncommitted or ignored files, and skips production repositories. Manual actions on production repositories require the repository name.

Forget missing worktrees

A worktree folder may already be gone while the repository still lists it. Review the missing folders before confirming their cleanup.

This only forgets missing, unlocked worktrees. Files and local branches stay in place. Locked entries are kept. The removed entries also disappear from your watched folders; locked entries stay watched.

This review does not delete an existing worktree or discard unmerged work. A changed preview or a problem with an entry for an existing folder stops cleanup. Production repositories still require typed-name confirmation.

If a remote branch is missing

A branch disappearing from the remote does not prove your local work was pushed or merged. Keep the local branch and review its commits in Git. Do not delete local work just to clear a missing-remote message.

Back to the Guide · Need a hand? Contact us