finishing-a-development-branch

To finalize a development branch, this workflow verifies your tests pass and then presents four explicit options for integrating the work, including local merges, pull request creation, branch retention, and worktree cleanup.

When merging a finished feature branch, you can choose from four structured options: perform a local merge, create a pull request, retain the branch without merging, or execute safe worktree cleanup.

Yes, you can create a pull request when finishing development work by selecting the PR creation option from the four structured choices presented automatically after your test suite passes.

Yes, finishing a development branch requires tests to pass first, as the workflow explicitly enforces test verification before detecting the base branch and presenting any integration options.

The best way to clean up worktrees after merging is using the optional post-workspace cleanup process, which safely removes worktree directories after you select your preferred branch integration option.

Base branch detection works by automatically identifying your project's main branch during feature completion, ensuring the suggested merge workflows and pull request targets align correctly with your repository structure.