finishing-a-development-branch

To safely merge a git feature branch, you must validate that tests pass first, identify the correct base branch using git merge-base, and then select a structured integration option like a local merge or pull request.

The best way to clean up git worktrees after merging is to use a guided workflow that performs post-task workspace cleanup, preventing branch drift by removing obsolete worktrees and branches after your integration decision.

You can determine the correct base branch before creating a pull request by applying the git merge-base command, which identifies the appropriate integration target for your feature branch safely and accurately.

Yes, you can push a git feature branch without merging locally by choosing the explicit push and pull request creation option, which is one of four actionable outcomes provided during the branch finalization process.

Yes, finalizing a development branch requires test verification to ensure all tests pass before presenting any merge, pull request, keep worktree, or discard options for safe integration.

If a feature branch is ready but you want to discard it, you can select the explicit discard option provided among the four outcomes, which ensures proper cleanup of the worktree and prevents workspace drift.