finishing-a-development-branch

To finalize a development branch after tests pass, you validate tests and choose from four integration options: merge locally, push a pull request, keep the branch, or discard it. This ensures safe and auditable completion of feature work.

When merging a feature branch, you have exactly four options: merge locally into the base branch, push and create a pull request, keep the branch for later work, or discard the changes entirely. Post-merge worktree cleanup restores a clean state.

Yes, finishing a development branch requires baseline knowledge of the project's test command and base-branch naming. The workflow determines the target base branch automatically to ensure changes merge into the correct integration stream.

Yes, when discarding a feature branch or completing any integration action, the workflow performs post-worktree cleanup automatically. This removes the branch and restores the local repository to a clean state after the chosen action executes.

The best way to guide pull request creation is enforcing a four-option decision model that verifies tests pass first, then offers to push and create a PR. This standardizes the workflow and ensures safe, auditable branch integration.

You should verify tests before merging a development branch to ensure the feature work is stable. The workflow validates that tests pass on the branch before offering any integration or cleanup options, preventing broken code from entering the base branch.