finishing-a-development-branch

To finalize a git development branch after tests pass, you determine the base branch and select one of four integration paths: merge locally, push and create a pull request, keep the branch, or discard it. The workflow then performs cleanup based on your selection.

The best way to merge a completed development branch in a multi-branch workflow is to verify tests, determine the correct base branch, and choose between creating a local merge, opening a pull request, keeping the branch, or discarding changes, followed by worktree cleanup.

Yes, finishing a development branch requires local test verification before proceeding to create a pull request or merging. Ensuring tests pass is the mandatory first step before the four integration options are presented for selection.

Yes, you can discard changes and clean up worktrees when finishing a development branch. Discarding is one of the four explicit options provided, automatically handling branch and worktree cleanup to maintain repository hygiene.

Besides a local merge, options for integrating a development branch include pushing to create a pull request, keeping the branch as-is for later work, or discarding the branch entirely. All paths include subsequent worktree and branch cleanup.

You should keep a development branch as-is instead of merging or discarding when development is incomplete or tests fail. This option pauses integration while preserving your work, skipping the final cleanup steps applied to merged or discarded branches.