finishing-a-development-branch

To safely merge a finished git branch, the workflow verifies passing tests, identifies the base branch, and requires explicit confirmation before executing a local merge, pull request creation, or discard action.

The best way to clean up git branches after feature work is to validate tests, select a completion path like merge or pull request, and apply workspace detection rules before executing any destructive branch deletion.

Git branch management in a named worktree or detached HEAD requires environment-aware detection of the specific checkout context before presenting the correct merge, pull request, or discard workflow.

You should verify test status before merging a git branch because test-first validation confirms the project test suite is passing, ensuring no broken code enters the base branch during the cleanup process.

To discard changes on a development branch safely, the workflow requires explicit confirmation before destructive actions, ensuring you intentionally choose to discard work after test validation and workspace detection are complete.