finishing-a-development-branch

To safely merge a git development branch, you need to verify tests pass first, then select the correct base branch for integration. This process ensures release readiness by gating the merge behind test verification and environment detection to prevent unsafe states.

The best way to clean up a named worktree after merging is using provenance checks for worktree ownership and conditional cleanup rules. Worktree cleanup only triggers for merge or discard actions, requiring typed confirmation before any permanent branch or commit deletion occurs.

Yes, you can open a pull request from a detached HEAD state. The environment-aware decisioning detects detached HEAD, normal repositories, and named worktrees, presenting the appropriate PR options with correct templates while ensuring safe integration decisions without accidental branch deletion.

To discard git branch changes without harming other worktrees, the discard process uses worktree provenance checks and requires typed confirmation. This ensures conditional cleanup only affects the target branch, preventing accidental deletion of commits or branches shared across other active worktrees.

Yes, branch workflow automation requires test verification before offering any merge or PR options. This test-first completion approach prevents broken or incomplete development work from being merged by enforcing the project's test suite as a precondition for safe integration.