finishing-a-development-branch

Finalizing a git feature branch involves verifying tests pass, detecting the base branch, then choosing from four explicit options: local merge, push PR, keep as-is, or discard, followed by worktree cleanup.

Closing a development branch deterministically presents four explicit workflow options: performing a local merge, pushing a pull request, keeping the branch as-is, or discarding it entirely.

You cannot close a git branch if tests are failing, because the workflow enforces test verification as a quality gate that prevents finalizing a feature branch until all tests pass successfully.

To clean up git worktrees after merging a feature branch, the workflow automatically performs post-action cleanup of related worktrees and resources based on your chosen finalization option to keep the repository tidy.

The branch finalization workflow does not require specific dependencies, as it operates with standard git worktree and branch structures to guide the closing process and clean up related resources deterministically.