finishing-a-development-branch

To safely finish a development branch, you should verify tests pass, then choose to merge to a base branch, create a pull request, or discard the work. This ensures a clean and efficient workflow exit.

The best workflow for merging a branch involves running test verification first, selecting a local merge to the base branch, and finally cleaning up the worktree. This standardized process prevents unresolved issues from entering the main codebase.

Yes, you can create a pull request after verifying your branch tests. The workflow presents structured options for integration, allowing you to select pull request creation and execute the chosen workflow with explicit confirmation.

To discard git changes and clean up your worktree, select the discard option from the structured workflow choices. The process safely removes the work with explicit confirmation and handles the subsequent worktree cleanup.

Yes, branch completion requires passing tests before merging to ensure code stability. The workflow automatically checks if tests pass before presenting integration options, guaranteeing a safe exit strategy for feature development.

You should discard a development branch instead of creating a pull request when feature work is no longer needed or tests fail irrecoverably. This option safely removes the work and cleans up the worktree with explicit confirmation.