finishing-a-development-branch

To safely finish a Git development branch, enforce a test verification step first, then choose from four options: merge locally, push for a pull request, keep the branch, or discard it. Worktree cleanup follows automatically for merge, PR, or discard actions.

Integrating a development branch offers exactly four structured options: merge locally, push and create a pull request, preserve the branch indefinitely, or discard it. This eliminates ambiguous decision loops after completing your work.

No, discarding a branch and its worktree requires explicit typed confirmation. This safety mechanism prevents permanently losing commits and ensures you intentionally approve the destructive deletion action.

Prevent merging broken code by enforcing a test-first completion gate. This workflow requires verifying that the full test suite passes before presenting any merge, pull request, keep, or discard options for your feature branch.

Yes, worktree cleanup occurs automatically when you choose to merge locally, push for a pull request, or discard the branch. If you select to preserve the branch, the worktree is retained without modification.

The best way to avoid unsafe Git integration is using a structured branch completion workflow that mandates test verification and provides four explicit actions. This prevents accidental merges or deletions by requiring typed confirmation for destructive operations.