finishing-a-development-branch

Finalizing a git development branch requires verifying tests, determining the base branch, and choosing to merge locally, create a pull request via GitHub CLI, or preserve the branch. It also handles worktree cleanup to ensure a tidy environment.

The best way to merge local code changes and clean up a git worktree is to use an automated workflow that performs local merges, verifies tests, and executes selective worktree cleanup after successful code integration.

Yes, this workflow generates a pull request using the GitHub CLI. It presents structured options for pull request creation, local merges, or branch preservation after mandatory test verification passes.

You can discard work on a development branch safely because the workflow provides explicit confirmation steps for destructive actions. It enforces mandatory test verification before allowing any code integration or branch discarding.

To verify tests pass before merging a git branch locally, the workflow automatically checks your tests during the code integration process. Mandatory test verification ensures code quality before any local merges or pull request generation proceeds.

You should preserve a branch instead of merging code changes when you need to keep work isolated for future development. The workflow presents branch preservation as a structured option alongside local merges and pull request creation.