finishing-a-development-branch

To safely merge a git feature branch, the workflow requires running and verifying passing test suites first, detecting the base branch, then presenting structured options like local merge or push-and-PR before executing the integration.

Cleaning up git worktrees after merging involves conditional worktree removal executed during the branch finalization process, ensuring no orphaned worktrees remain after a local merge or discard action is completed.

You can discard a git development branch safely by requiring explicit typed confirmation for destructive deletes, ensuring the branch is only removed after intentional user verification during the discard workflow.

Yes, the branch management workflow supports creating pull requests directly by offering a push-and-PR option that pushes the branch and creates a pull request with a prepared description after test verification.

You need to verify tests before finalizing a development branch whenever the branch has implementation and tests and requires end-of-life actions like local merge, push-and-PR, preserve, or discard to prevent broken merges.

The options for finalizing a completed feature branch are exactly four choices: merge locally, push and create a pull request, keep the branch preserved, or discard the work with typed confirmation.