finishing-a-development-branch

To safely finish a git branch after tests pass, verify readiness and choose to merge locally, push for a pull request, preserve, or discard the work. This prevents unsafe integration by applying explicit user choice handling.

The best way to merge a feature branch locally without losing work is to use a structured workflow that presents clear completion options and applies worktree cleanup rules only when appropriate, reducing the risk of accidental loss.

Worktree cleanup when discarding a development branch works by handling branch deletion and workspace removal only when explicitly chosen, reducing the risk of accidental loss while ensuring unsafe integration is prevented.

Yes, you can push a feature branch for a pull request without merging it locally. The workflow verifies tests pass and presents clear branch completion options, allowing you to push for a PR while keeping the branch intact.

You need to verify tests before completing a git branch when you are ready to close out completed development work. Test verification confirms the project suite passes before any merge, pull request, or discard decision is made.

Yes, this branch completion workflow requires base-branch detection to coordinate the safe completion of a development branch. It ensures the correct integration path is identified before applying worktree cleanup rules or merging.