finishing-a-development-branch

Finishing a git feature branch involves verifying tests pass, choosing to merge or create a pull request, and cleaning up the worktree. This process enforces test verification before allowing integration and safely removes the local worktree afterward.

Before merging a development branch, run the project's test suite to ensure all tests pass. The workflow blocks progression if verification fails, then determines the correct base branch and executes the merge only after explicit confirmation.

Yes, you can discard work and delete a git worktree safely by selecting the discard option. This action requires typed confirmation before executing forced deletes and removing the worktree, preventing accidental data loss during branch cleanup.

To clean up git worktrees after a branch merge, select the local merge option during the workflow. Once the merge is confirmed and executed, the process automatically removes the associated worktree to leave the repository tidy.

When a feature branch is complete and tests pass, your integration options are merge locally, push and create a pull request, keep the branch for further work, or discard the work entirely. Each option includes appropriate cleanup and confirmation steps.

Branch integration fails when tests do not pass because automated test verification blocks progression. This enforcement ensures that only verified code with a passing test suite can be merged, pushed for a pull request, or otherwise integrated into the base branch.