finishing-a-development-branch

To finalize a git development branch after tests pass, you select from four deterministic integration options: merge, create a pull request, keep, or discard. It guides post-implementation integration based on verified test results.

The best way to merge a finished feature branch is to verify test results first, then select a deterministic integration path. This workflow presents structured options for merging, creating a pull request, or discarding work based on the detected base branch.

Yes, you can create a pull request after verifying test results. The workflow presents pushing a PR as one of four structured options for integrating your finished feature work, alongside merging, keeping, or discarding the branch.

Yes, this workflow supports cleaning up git worktrees after merging. Based on your chosen integration path, it optionally preserves or cleans up worktrees to maintain a tidy development environment for collaborative projects.

You should discard a feature branch instead of merging when test verification fails or the work is no longer needed. The workflow presents discarding as one of four deterministic options, allowing you to cleanly remove unwanted work and clean up the worktree.