finishing-a-development-branch

To safely finish a git development branch, you need a structured workflow that validates tests, checks repository state, and guides your integration decision between merging, creating a pull request, or discarding changes. This process prevents accidental work loss.

Yes, git worktree workflows are fully supported. The process adapts to named branch worktrees and detached HEAD states, applying specific cleanup rules to safely remove the worktree without losing uncommitted development work.

The best way to clean up local branches after a pull request merge is to follow a structured completion workflow that verifies your tests pass and applies safeguards against unsafe branch removal before deleting the integrated development branch.

Yes, branch completion workflows handle detached HEAD states in git by detecting the environment and applying appropriate cleanup rules. This ensures you can safely discard changes or integrate work without accidental loss in detached states.

You need to verify tests before merging a development branch to confirm implementation readiness. This validation step is a required safeguard in the completion workflow to ensure you do not integrate broken code into the main repository.

To keep development work without merging immediately, select the option to retain changes during the branch completion workflow. This safely pauses integration while preserving your current repository state and branch environment.