finishing-a-development-branch

To verify tests before merging a git feature branch, inspect the branch state and run test validation to confirm the work is ready. This ensures all checks pass before proceeding with pull request creation or local merge execution.

The best way to close out a finished development branch is to validate tests and choose from four structured completion options: merge locally, open a pull request, keep the branch, or discard it. This structured approach eliminates guesswork during the merge workflow.

To safely clean up a git worktree after merging a feature branch, use safe cleanup handling that manages branch deletion only when integration is complete. This prevents accidental loss of work during the final worktree cleanup process.

You should open a pull request instead of merging a branch locally when your software engineering workflow requires peer review before final integration. Both are valid completion options presented after test verification succeeds on the feature branch.

Yes, you can keep a development branch instead of discarding it after tests pass. Keeping the branch is one of the four explicit completion choices available, allowing you to delay the merge workflow or worktree cleanup without losing the verified work.