finishing-a-development-branch

To decide whether to merge a git branch locally or push a pull request, use an automated workflow that validates test results and presents four deterministic choices: merge locally, push a PR, keep the branch, or discard it.

The best way to clean up temporary git worktrees after a merge is to use a workflow that executes your chosen integration action and automatically performs worktree cleanup after the merge, PR, or discard operation completes.

To enforce that tests pass before integrating a development branch, apply a Git workflow protocol that validates test results before offering any integration options, blocking merges or pull requests until tests succeed.

Yes, you can automate discarding a git branch by using a branch management workflow that offers exactly four options, allowing you to select the discard action to remove the branch and clean up any temporary worktrees.

You should keep a development branch instead of merging it into the mainline when integration is not yet desired, selecting the keep option from a four-choice workflow protocol that defers merging, PR creation, or discarding.