finishing-a-development-branch

To finish a git development branch, you verify passing tests, determine the base branch, and select one of four integration options: merge locally, push a pull request, keep the branch, or discard it with standardized cleanup.

The best way to merge a feature branch depends on your workflow: merging locally integrates changes directly to the base branch, while pushing a pull request creates a remote PR for peer review before completing the branch cleanup.

You can keep your git feature branch instead of deleting it by selecting the explicit option to retain it, which pauses the cleanup workflow and leaves the branch intact for future development.

You should verify tests before choosing a branch integration option because the workflow enforces test validation as a guardrail, ensuring only fully tested code proceeds to local merges, pull requests, or branch discarding.

To discard a git development branch safely, you select the discard option from the structured choices, which initiates a standardized cleanup workflow to remove the branch and prevent unresolved merge conflicts.

You should not use a standardized workflow for finishing a development branch when your implementation and tests are not yet complete, as the process requires passing test verification before presenting any merge or pull request options.