finishing-a-development-branch

Run the full test suite first, confirm the base branch the work forked from, then check out the base, pull, and merge. Re-run tests on the merged result before deleting the feature branch or removing any worktree.

Change directory to the main repository root, then run git worktree remove followed by git worktree prune. Only remove worktrees under .worktrees/ or worktrees/ that your tooling created; leave externally managed workspaces in place.

A refusal means the worktree contains modified or untracked files that exist nowhere else. List them with git status --porcelain -uall, then commit them, move them to the main repo, or explicitly delete them. Never use --force without confirming with the user.

A detached HEAD cannot be merged back directly since there is no named branch. Instead, push it as a new branch with git push origin HEAD:refs/heads/<new-branch> and open a pull request, or keep the workspace as-is.

Discarding should only happen when the user explicitly requests it, and only after a typed confirmation listing the branch, commits, and worktree to be deleted. The branch is then force-deleted with git branch -D after worktree cleanup.