finishing-a-development-branch

To finalize a git feature branch, you validate CI tests, select an integration path from structured options, execute the chosen workflow, and perform branch cleanup to keep the mainline clean.

The best way to merge a completed development branch is using a workflow that validates tests, identifies the base branch, and presents explicit actions like local merge, push PR, keep, or discard.

Yes, you can use pull requests for branch integration. The workflow presents push PR as one of four explicit actions alongside local merge, keeping the branch, or discarding it entirely.

Branch cleanup after a git merge handles branch hygiene and optional worktree cleanup automatically once your chosen integration workflow executes, ensuring a safe and traceable handoff.

Yes, CI tests must pass before merging a development branch. The workflow enforces test verification to ensure safe integration before presenting any structured merge or discard options.

You should discard a git branch instead of merging when the completed work is no longer needed. The workflow presents discarding as one of four explicit actions to safely remove unwanted branches.