finishing-a-development-branch

To finalize a development branch, you can verify tests pass and choose to merge locally, push and create a pull request, keep the branch as-is, or discard it entirely. This guided workflow prevents ambiguity during final integration.

The best way to merge a feature branch locally is to verify tests pass first, identify the correct base branch, and then execute a local merge. This workflow safely integrates completed work while respecting auto_commit configurations.

Yes, you can push your completed development branch and create a pull request. This workflow verifies tests pass beforehand and presents push and create PR as one of four explicit finalization options.

To discard a development branch and clean up worktrees, select the discard option from the finalization workflow. The process prompts for destructive actions to ensure safety and performs optional worktree cleanup after execution.

Yes, the branch finalization workflow verifies that tests pass on the feature branch before presenting integration options. This ensures completed work is validated before you merge locally or create a pull request.

You should keep a development branch as-is when you are not ready to finalize integration. This option preserves the current branch state without merging, pushing, or discarding, allowing you to resume work later.