finishing-a-development-branch

To finish a git feature branch safely, verify tests pass first, then choose from structured options: merge locally, push and create a PR, keep as-is, or discard. The workflow enforces safety checks and manages workspace cleanup after completion.

The best way to clean up a git worktree after merging is to use a structured workflow that detects your repository state and manages workspace cleanup automatically, removing artifacts after you choose to merge or discard the branch.

Yes, you can create a pull request from a detached HEAD state. The workflow detects repository states including normal repos, named worktrees, and detached HEAD, tailoring the available actions like push and create PR accordingly.

To discard a git branch and clean up the workspace, select the discard option provided by the structured workflow. This requires explicit confirmation before executing the discard action and managing the subsequent workspace cleanup.

When completing development on a feature branch, you have exactly four options: merge locally, push and create a pull request, keep the branch as-is, or discard it. All options require test verification before proceeding.

Yes, you need to run tests before merging a git branch. The workflow requires test verification to pass before presenting the structured options to proceed with integration, ensuring the branch is safe to complete.