finishing-a-development-branch

To safely merge a git development branch, this workflow enforces mandatory test verification before proceeding and presents structured options for local merging. It prevents broken code integration by requiring all project tests to pass before allowing any branch finalization.

To prevent accidentally deleting committed work when discarding a git branch, the workflow requires explicit typed confirmation for destructive discard operations. This safe destructive action guard ensures you cannot accidentally remove committed branch work without deliberate verification.

The best way to clean up unused git worktrees after completing a feature branch is to automate worktree cleanup during the branch finalization process. This maintains a clean local repository state by automatically removing worktrees for completed or discarded branches.

Yes, you need to run tests before creating a pull request for a feature branch. The workflow enforces mandatory test verification, automatically checking that all project tests pass before allowing any PR creation or merge actions to prevent untested code from being integrated.

Yes, you can keep a development branch as-is without merging or discarding it. The workflow presents exactly four structured completion options, including keeping the branch for future work, alongside local merge, pull request creation, or discard actions.

The options for finishing a git bug fix or refactor branch include local merging, pull request creation, keeping the branch as-is, or discarding the work. These four structured choices eliminate decision fatigue and ensure consistent branch finalization workflows.