finishing-a-development-branch

Automate git branch cleanup by verifying your test suite passes, then following a guided menu for merging, pull request creation, or branch deletion to ensure safe integration.

The best way to merge a development branch safely is to enforce automated test verification first, ensuring code integrity before executing any repository modifications or branch deletions.

Worktree removal occurs only after verifying the success of your chosen integration path, handling complex detached HEAD states and branch deletion to clean up the repository environment.

Yes, you need git and standard testing frameworks to validate code integrity, as the workflow requires all tests to pass before allowing integration steps to proceed.

Yes, the workflow is environment-aware and automatically detects if you are in a standard repository or a detached HEAD worktree to present only valid integration options.

Verifying test status before deleting a git branch ensures code integrity, preventing the loss of unmerged changes by confirming the success of the integration path first.