finishing-a-development-branch

To safely merge a git feature branch, you can run the test suite first and then choose between merging locally, creating a pull request, keeping the branch, or discarding it. This ensures tests pass before any integration action proceeds.

Finalizing a development branch involves verifying that all tests pass before offering structured choices for integration. You can push and create a pull request, merge locally, keep the branch as-is, or discard it with confirmation.

The GitHub CLI is optional for creating a pull request from a feature branch. The core workflow requires the git CLI and access to the repository's test suite commands, but uses the GitHub CLI specifically for automated PR creation.

You cannot discard a git worktree and branch if tests fail because the workflow stops when any test fails. Safety checks require passing tests before proceeding, and destructive discard actions require explicit confirmation.

Automated branch cleanup performs the selected Git workflow, including worktree removal and branch deletion when appropriate. It only triggers after tests succeed and you choose to merge or discard the branch.

Use a structured workflow to finish a development branch when you need a guided, error-free way to integrate or dispose of feature work. It is ideal for developers who want test verification and clear integration options without manual Git errors.