finishing-a-development-branch

To verify tests before merging a git development branch, this workflow runs your project test suite and hard-blocks completion if tests fail, ensuring only passing changes move forward.

When finishing a development branch, you get exactly three deterministic options: merge to main via a pull request, create a pull request without merging, or keep the branch as-is for later review.

Yes, the branch completion workflow runs CI checks by executing your project test suite as an authoritative gate, and optionally runs an advisory acceptance-oracle if a plan path is available.

Worktree cleanup is performed only when you select the merge via pull request option to finalize your release workflow; the other two branch completion paths preserve your working state.

Yes, you can keep a development branch as-is instead of creating a pull request, which parks your work safely for later review without triggering worktree cleanup or a merge to main.