finishing-a-development-branch

To safely merge a development branch after testing passes, you can choose to merge locally, push and create a pull request, keep the branch as-is, or discard the work entirely. The workflow enforces test verification before presenting these integration options.

When finishing a git branch after tests pass, you have exactly four options: merge locally into the base branch, push and create a pull request, keep the branch as-is for later work, or discard the work and clean up.

Base branch detection automatically identifies the target branch for integration during the git workflow completion process. It ensures your finished work merges or creates a pull request against the correct parent branch without manual configuration errors.

Yes, you can clean up git worktrees automatically after merging a development branch. The workflow includes worktree cleanup as part of its discard or merge options, removing leftover working directories once integration is complete.

The best way to discard git branch changes is to select the discard option during the workflow completion process. This safely removes the work and cleans up associated worktrees, ensuring no orphaned branches or directories remain.

Yes, you need to run tests before creating a pull request. The workflow strictly enforces test verification before presenting any integration options, ensuring that only verified code is pushed or merged into the base branch.