finishing-a-development-branch

To merge a development branch after tests pass, you can use a structured workflow that validates test results, determines the base branch, and presents explicit options to merge locally, push a pull request, keep the branch, or discard it.

The best way to clean up a git worktree after finishing a feature branch involves selecting an explicit integration path, which then triggers the corresponding worktree cleanup actions based on your chosen merge or pull request workflow.

Yes, you can create a pull request while keeping the feature branch by selecting the explicit PR creation option, which allows you to push the branch for review without immediately discarding your local worktree environment.

Determining the correct base branch before merging git work is handled automatically by the finalization workflow, which inspects your branch management setup to identify the target base branch before presenting integration options.

You should verify tests before choosing a git merge option because the finalization workflow enforces test validation as a prerequisite, ensuring implementation is complete and preventing broken code from entering the base branch.

Yes, the branch finalization workflow supports keeping the branch by offering four explicit options, allowing you to pause integration and preserve the current development state within your worktree instead of merging or discarding.