superpowers-finishing-a-development-branch

Finishing a development branch involves choosing one of four integration outcomes: merge locally, push and create a pull request, keep the branch, or discard it. The workflow requires a validated test suite and base branch knowledge to execute the chosen path with final cleanup steps.

Choosing between merging locally or creating a pull request depends on your team's need for auditable integration. The workflow presents four explicit outcomes to select from, reducing ambiguity and guiding the specific merge, PR, or cleanup actions required.

Yes, a validated test suite is required before proceeding with branch integration. The workflow is test-verified, meaning tests must pass before you choose an outcome, and it provides steps for validating the merged result after the action is complete.

A development branch cleanup workflow covers the complete lifecycle from identifying the base branch to performing final cleanup. It includes selecting one of four predefined outcomes and executing accompanying cleanup steps to resolve how completed work is integrated.

Yes, you can keep the branch or discard it. The workflow presents four explicit outcomes: merge locally, push and create a pull request, keep the branch, or discard it, allowing you to resolve code integration without forcing a merge into the base branch.