finishing-a-development-branch

To safely merge a completed git feature branch, this workflow first verifies that all project tests pass, then guides you through a structured local merge to prevent broken integrations and messy git history.

The best way to clean up a git worktree after feature development is using a guided completion workflow that automatically handles worktree cleanup only for appropriate paths, preventing lost work and messy repositories.

You can create a pull request after finishing a development branch safely because the workflow enforces test verification before offering the push and create PR option, ensuring broken code is not submitted for team review.

You can discard a feature branch safely if the implementation is no longer needed by selecting the discard option, which requires explicit confirmation for this destructive action to prevent accidental loss of work.

Yes, this branch completion workflow automatically checks that all project tests pass before offering any integration options, including local merge, to ensure you do not integrate broken code into your main branch.

When finishing a development branch, your options include a local merge, pushing to create a pull request, keeping the branch as-is, or discarding the work, all managed with appropriate guardrails.