finishing-a-development-branch

To safely merge a development branch, you should verify your test suite first, then choose a specific integration path like merging locally or opening a pull request. This structured workflow prevents incomplete code from being integrated.

Cleaning up a git worktree after merging depends on your integration decision. Worktree removal is executed automatically when you choose to merge locally or discard the branch, while preserving it if you keep the branch as-is.

Running tests before opening a pull request acts as a completion gate that stops integration immediately if the test suite fails. You must ensure deterministic test execution to verify your feature branch is safe to push.

Discarding a git branch requires typed confirmation to guard against destructive deletion. This safety mechanism ensures you intentionally remove the branch and its associated worktree only when you are certain the work is no longer needed.

Effective branch management does not require you to manually specify the base branch, as the workflow detects the most likely base branch automatically. It then presents four explicit options to guide your integration decision.

Keeping a development branch instead of merging allows you to preserve unfinished work for later review or continued development. This option leaves your worktree intact while deferring the integration or discard decision.