finishing-a-development-branch

To finalize a Git feature branch after tests pass, a structured workflow verifies test success, determines the base branch, and presents explicit merge, pull request, or discard options to safely integrate completed development work.

The best way to clean up local Git branches after merging is to use a workflow that offers optional post-merge cleanup for worktrees and branches, applying safeguards to prevent data loss during the finalization process.

Yes, you can choose between opening a pull request and merging locally when finishing a development branch. The workflow provides four explicit completion options: merge locally, push and open PR, keep the branch, or discard changes.

Yes, the branch finalization workflow verifies that tests pass before completing and presenting integration options. This ensures test success is validated prior to base-branch determination and the execution of any merge or cleanup actions.

To prevent data loss when deleting Git worktrees and feature branches, use a finalization workflow that includes built-in safeguards during post-merge cleanup, ensuring branches are only removed after successful integration.