finishing-a-development-branch

To safely merge a git feature branch, the system first runs tests to verify a releasable state, detects the base branch, and then presents a local merge as one of four structured completion options, ensuring clean branch handoff without accidental data loss.

The best way to clean up git worktrees during branch discard is to require explicit confirmation for the destructive deletion action before automatically removing the associated worktrees. This prevents accidental loss of unreviewed work while ensuring the local environment is tidied up.

Yes, you can create a pull request directly from a local development branch. After verifying that all tests pass, the workflow presents pull request creation as a structured handoff option alongside local merge, keeping, or discarding the completed feature work.

Yes, finishing a development branch requires passing tests first. The workflow applies test gatekeeping to check that the project is in a releasable state before offering any completion actions like merging, pull request creation, or discarding the work.

To keep a git branch for later use without merging, you select the preserve work option from the structured handoff decisions presented after tests pass. This leaves the development branch intact and skips any worktree cleanup associated with finalizing or discarding.