finishing-a-development-branch

Finishing a development branch after tests pass involves discovering the base branch and choosing one of four explicit options: merge locally, push and create a pull request, keep the branch, or discard the work.

When a feature branch is complete, you have four workflow options: merge it locally into the base branch, push and create a pull request, keep the branch as-is for later, or discard the work entirely.

A Git workflow handles post-merge cleanup by executing the chosen merge or pull request option and then performing optional worktree cleanup to remove leftover branch artifacts.

Yes, you can create a pull request by selecting the explicit push and create PR option presented when finishing your development branch, which safely executes the workflow against the determined base branch.

The best way to discard a Git branch after implementation is to select the explicit discard work option provided during the branch finishing workflow, which safely removes the changes.

Yes, you need to verify that tests pass before finishing a development branch, as the workflow requires successful test verification before presenting the four merge, PR, keep, or discard options.