finishing-a-development-branch

To safely merge a git feature branch after tests pass, the workflow verifies tests first, identifies the correct base branch, then executes the merge locally or pushes to open a pull request. It presents four structured options to eliminate ambiguity.

The best way to clean up git worktrees after finishing a branch is to use a workflow that removes worktrees only when appropriate. It executes git operations for merge, push, or delete, and performs worktree cleanup with explicit typed confirmation for destructive actions.

Yes, you can push a feature branch and open a pull request without merging locally. The workflow offers this as one of four fixed options, executing the git push command and preparing the branch for review after verifying that tests pass.

To discard a git feature branch without accidental deletions, the workflow requires explicit typed confirmation before executing destructive git commands. This ensures you consciously approve the deletion of the branch and associated worktree only when intended.

Yes, finishing a feature branch requires passing tests before integration. The workflow enforces test-first verification, demanding that tests pass before allowing any merge, push, or destructive action to proceed on the feature branch.

You should preserve a git branch instead of merging when implementation is complete but you want to keep it for later work. The workflow offers a dedicated option to keep the branch active without merging or discarding, preventing premature integration.