finishing-a-development-branch

To safely merge a git feature branch after tests pass, the workflow verifies test status and identifies the correct base branch before presenting options to merge locally, push for a pull request, keep the branch, or discard it with confirmation.

The best way to clean up git worktrees after development work involves following a safe cleanup flow that activates once tests pass, providing explicit options to finalize integration or discard the work while safely removing associated worktrees.

Yes, this git workflow enforces test verification before proposing any merge or pull request actions, applying guardrails that prevent unsafe merges or branch deletions until tests successfully pass.

Determining the correct base branch when finishing a development branch is handled by the workflow, which outlines how to identify the target base branch before presenting explicit merge, pull request, or cleanup options.

You can discard git branch changes safely by selecting the explicit discard option, which requires confirmation and applies workflow guardrails to prevent unsafe or accidental branch deletions.