finishing-a-development-branch

Finalizing a development branch involves verifying tests, identifying the base branch, and selecting an integration path: merge locally, push a pull request, keep the branch, or discard it. This enforces a deterministic decision flow with corresponding cleanup steps.

The options for finishing git branch work are merging locally, pushing and opening a pull request, keeping the branch as-is, or discarding it. This fixed decision flow automates cleanup and reduces ambiguity once implementation is complete.

To merge a git worktree locally after implementation, select the local merge option from the finalization flow. This requires passing tests first, identifying the base branch, and executing the corresponding cleanup steps for the merged worktree.

Yes, you can push a pull request instead of merging locally. The finalization flow presents both options, allowing you to push your work and open a PR while performing the necessary branch cleanup steps after tests pass.

You should discard a branch instead of merging when the implementation is no longer needed. After verifying tests, the finalization flow offers a discard option that performs the required cleanup steps to remove the branch and worktree.

Yes, passing tests are required before creating a pull request. The finalization flow applies when implementation is complete, enforcing test verification before presenting the options to push a PR, merge locally, keep, or discard the branch.