finishing-a-development-branch

To merge a git development branch after tests pass, you use a workflow that verifies tests, detects the base branch, and presents structured options like local merge or push-PR to finalize the feature branch integration.

Options for finishing a feature branch in git include performing a local merge, pushing to create a pull request, keeping the branch active, or discarding the work, with optional cleanup of worktrees after the chosen action.

Yes, test verification is required before creating a pull request or executing a local merge. This ensures the feature branch is stable and provides a safe, auditable path before integrating completed work into the base branch.

The best way to clean up a git worktree after merging is to use a workflow that executes optional cleanup steps automatically after you select a merge or discard path for your completed feature branch.

Yes, you can discard a completed feature branch instead of merging it. The workflow provides exactly four structured options, including discarding the work and keeping the branch, allowing flexible branch management.