workflow-finish

To clean up git branches and worktrees after a PR merge, you need to delete local and remote branches, remove associated worktrees, and prune references. This ensures your repository stays free of stale branches and lingering workflow contexts.

The safest way to delete branches after merging is to verify the PR merge status before deletion and switch to the main branch if needed. Ignoring resources that have already been removed ensures the cleanup operation remains idempotent.

Removing a git worktree and its workflow context involves deleting the worktree directory, pruning references, and removing the specific workflow context directory for the branch. This updates status reports and clears lingering configurations.

Yes, you can clean up merged branches by specifying the current branch, a ticket number, or an explicit branch name. This flexibility allows targeted cleanup of specific PR workspaces without affecting other active branches.

Yes, the branch cleanup process uses a shared configuration from .claude/workflow-config.json. This file centralizes settings to ensure the workflow finish operation correctly identifies and removes the appropriate branches and worktrees.

Running the cleanup workflow on already deleted git branches is safe because the operation is idempotent. It automatically ignores resources that have already been removed, preventing errors during the branch and worktree deletion process.