finishing-a-development-branch

To finish a development branch, you verify tests pass, determine the base branch, and select one of four options: merge, submit a pull request, keep the branch, or discard work. The workflow then executes the chosen option and cleans up temporary worktrees.

When finishing a development branch, you have four concrete options: merge directly, submit a pull request, keep the branch for future work, or discard the work entirely. The workflow presents these paths after verifying test stability.

You should run a git branch cleanup workflow once your feature implementation passes tests and you are ready to finalize development work. It guides teams through test verification and base-branch determination before presenting merge or discard options.

Yes, discarding work is one of the four concrete options presented by the development branch finishing workflow. You can select this path to safely conclude development work and execute post-action cleanup of temporary worktrees without merging.

No, the workflow dynamically determines the base branch for your software project before presenting the four options. It requires test verification first, then identifies the correct base branch to guide the merge, pull request, keep, or discard decision.