finishing-a-development-branch

To finish a development branch safely, verify tests pass, detect the base branch, then choose to merge locally, create a pull request, keep the branch, or discard it. The workflow executes git and gh commands with typed confirmation for destructive actions and cleans up worktrees when appropriate.

Yes, you can automatically merge a feature branch locally. The workflow detects the base branch, such as main or master, and presents merging locally as one of four explicit completion options, executing the git commands required to finalize the merge after tests pass.

The best way to discard a git feature branch without accidental data loss is using a workflow that requires typed confirmation for destructive actions. This ensures branch deletion and worktree removal only execute when explicitly confirmed by the user.

Yes, this branch management workflow requires passing tests before allowing a merge. Test verification gating ensures all tests must pass before any merge, pull request, or destructive discard action is offered or executed in the git repository.

To clean up a git worktree after finalizing a feature branch, the workflow applies safe worktree removal rules. It automatically deletes the worktree only when appropriate, such as after a successful merge or confirmed discard, protecting active work from accidental deletion.

You should keep a development branch when implementation is complete but you are not ready to finalize the work. The workflow presents keeping the branch as-is as one of four explicit options, preserving the worktree and branch for later action without executing destructive commands.