skill-finish-branch

Safely finishing a Git feature branch involves verifying test results, determining a safe base branch, and selecting a finalization action like merging, creating a pull request, keeping, or discarding the branch with optional worktree cleanup.

Git branch finalization in a collaborative workflow is best managed by enforcing guardrails such as test verification, explicit user choice for finalization actions, and post-action worktree cleanup to prevent accidental loss of work or destabilization of main branches.

Yes, creating a pull request is one of the four explicit finalization options presented when completing a feature branch, serving as a guarded alternative to merging locally, keeping, or discarding the branch.

To clean up Git worktrees after merging a branch, the finalization process includes an optional post-action cleanup step that removes worktrees and branches to maintain a clean mainline after the chosen completion action is performed.

You should discard a feature branch instead of merging it when the work is no longer needed, using the explicit discard finalization option which safely removes the branch and handles optional worktree cleanup to maintain repository integrity.

Yes, Git branch finalization verifies test results before concluding a branch, ensuring tests pass as a guardrail before presenting the option to merge, create a pull request, keep, or discard the branch.