finishing-a-development-branch

To safely finish a git branch, verify the test suite passes first, then choose to merge locally, open a GitHub pull request, preserve the branch, or discard it. Controlled worktree cleanup follows with explicit confirmation for destructive actions.

Worktree cleanup after completing a feature branch requires explicit confirmation before any destructive actions occur. Safe git operations ensure branch deletion and worktree removal happen only when appropriate, preventing accidental loss of unmerged work.

Yes, creating a GitHub pull request from a local development branch is one of the fixed integration choices presented after test validation. The workflow detects the base branch and guides the pull request creation as part of the branch handoff.

To discard a finished feature branch safely, select the discard option from the presented integration choices after tests run. The workflow isolates the destructive deletion and worktree cleanup, requiring explicit confirmation before removing the branch.

Yes, test validation is required before any branch integration options are offered. The test suite must pass to ensure branch readiness, preventing premature merges and unclear handoffs before presenting the choice to merge, pull request, keep, or discard.

A structured workflow to complete a feature branch prevents unsafe cleanup and guesswork by enforcing test validation, detecting the base branch, and presenting fixed integration choices. Standard git commands lack built-in safeguards against premature merges and accidental worktree deletion.