finishing-a-development-branch

To finish a git branch, you first verify tests pass, then choose an integration action like a local merge or pull request. The workflow identifies the base branch, executes the chosen git action, and confirms any destructive cleanup before finalizing the development branch.

The best way to clean up a git worktree after merging is to use a structured branch completion workflow that performs optional worktree removal. It safely discards the finished development branch only after confirming the integration action is complete.

Yes, you can create a pull request directly from a local development branch. A structured branch finishing workflow identifies the base branch for integration and guides pull request creation once test verification is confirmed.

Yes, you need to run tests before merging a git branch. Test verification is the required first step in a structured branch completion workflow to ensure the codebase is ready before any merge, pull request, or cleanup action is executed.

To discard a finished git branch without losing work, use a workflow that requires explicit confirmation for destructive cleanup. It ensures the branch is fully integrated or explicitly marked for discard before removing the branch or its worktree.

You should keep a git branch instead of merging or discarding it when you need to pause integration but preserve completed implementation work. A structured workflow offers keeping the branch as a valid end-of-branch outcome after tests pass.