finishing-a-development-branch

To safely merge a Git feature branch, you should run pre-merge test verification to ensure all tests pass before choosing to merge locally, create a pull request, or discard the work with explicit confirmation prompts.

Cleaning up Git worktrees requires environment-aware checks to only remove worktrees created by your tool, avoiding accidental deletion of host-managed workspaces and ensuring reliable workspace cleanup after branch integration.

Discarding incomplete Git feature branch work requires explicit confirmation prompts for destructive actions, ensuring you safely abandon unwanted code changes without risking accidental data loss to your main workspace.

Yes, environment-aware completion processes adapt available actions for detached HEAD states, named worktree branches, and normal Git repos to match your current workspace setup and safely push a pull request.

Verifying tests before merging a Git feature branch prevents integrating broken code into the main branch, enforcing test verification ensures reliable branch integration and saves developer time by avoiding broken merges.

Automated Git branch cleanup tools are limited by worktree provenance checks, meaning they will only clean up worktrees created by the tool itself and will not remove host-managed workspaces to protect your environment.