finishing-a-development-branch

To safely merge a git development branch, you must enforce mandatory test verification before offering any merge options, applying structured guardrails and environment-aware workflows across normal repositories, named worktrees, and detached HEAD states to prevent accidental code loss.

The best way to clean up unused git worktrees and branches is through an end-to-end workflow that manages local merges and PR creation, followed by automated worktree cleanup for harness-managed workspaces with mandatory confirmation before discarding work.

Yes, you can create a pull request from a detached HEAD or named worktree environment because the workflow detects your current git environment and presents only relevant, safe completion options like PR creation tailored to that specific state.

To prevent broken code from being merged, you must execute pre-completion test verification that automatically checks and ensures all project tests pass before offering any branch integration or pull request creation options.

Yes, this branch completion workflow works across normal repositories, named worktrees, and detached HEAD environments by applying environment-aware option presentation to ensure safe merges, PR creation, and worktree cleanup for each specific context.

You need mandatory confirmation when discarding work during branch cleanup because it acts as a guardrail against accidental code loss, ensuring that unused branches and worktrees are removed only after explicit user approval.