branch-completion

To safely complete a git feature branch after tests pass, you can use an automated workflow that verifies tests as a mandatory gate before offering structured completion options like local merge, push and pull-request, or cleanup.

The options for finishing a feature branch in a git workflow include local merge, push and pull-request creation, keeping the branch as-is, or discarding it with confirmation to ensure code quality before finalizing.

Branch cleanup after merging a feature branch works by executing deterministic actions that remove associated worktrees and delete the branch itself, ensuring the repository remains clean after a completion decision is made.

Yes, you can enforce a test verification gate before creating a pull request by using an automated process that mandates passing tests before presenting the option to push the branch and initiate a PR.

Yes, this branch completion workflow handles local merges and pull requests by presenting exactly four fixed options after verifying tests, allowing you to choose between local integration or remote pull-request creation.

You should discard a git branch instead of merging it when the development work is no longer needed, selecting the discard option with confirmation to safely remove the worktree and delete the branch.