finishing-a-development-branch

To safely merge a git feature branch, this workflow enforces automated test verification before allowing any integration actions, preventing broken code from being merged. You must pass all tests before proceeding with local merges or pull requests.

Cleaning up a git worktree after finishing a feature branch requires environment-aware detection to ensure safe removal. This workflow handles worktree cleanup only when safe and uses mandatory confirmation prompts to prevent accidental data loss.

Yes, you can create a pull request from a detached HEAD state because the workflow detects your current git environment and presents only the relevant, safe options. It adapts to normal repositories, named worktrees, and detached HEAD environments.

The best way to prevent accidental data loss when completing a git branch is using mandatory confirmation prompts before any deletion or discard actions. This structured workflow ensures branch retention or discard is always a deliberate choice.

Yes, this branch completion workflow works with named git worktrees by automatically detecting the environment and tailoring the available merge, pull request, and cleanup options to match the specific worktree context safely.

A structured workflow for finishing a development branch eliminates risky manual steps like skipping test checks or merging broken code. It enforces test verification and environment detection to prevent accidental work or worktree deletion.