exit-strategy

To finalize a git branch after verifying tests, the workflow confirms test results, determines the base branch, and presents four explicit options: merge locally, create a pull request, keep as-is, or discard.

The best way to clean up git worktrees and orphaned branches is using an automated safehouse management process during branch finalization, which ensures repository hygiene by discarding artifacts after selecting an exit path.

Yes, you can choose between merging locally and creating a pull request. The workflow presents four explicit finalization options: merge locally, push and create a PR, keep the branch, or discard the work.

Yes, the branch finalization process verifies test stability before merging. It automates a disciplined workflow that ensures stability by verifying test results before allowing you to select an exit path or perform cleanup.

You should discard a development branch when the work is no longer needed or fails stability checks. The workflow explicitly offers discarding as one of four finalization paths, followed by optional worktree cleanup.