finishing-a-development-branch

You can finalize a git workflow by selecting one of four structured options: local merge, push and create a pull request, keep the branch as-is, or discard the work entirely. Each path ensures explicit base-branch determination and handles optional cleanup.

To clean up local git branches after merging, select the local merge or pull request option. The workflow executes optional worktree and branch cleanup automatically, minimizing clutter and integration risk after finalizing your changes.

Yes, you can discard a development branch safely by choosing the discard option. This workflow path removes the specific feature branch and cleans the worktree, ensuring your base branch remains untouched during the cleanup process.

Yes, this git workflow requires tests to pass before creating a pull request. It verifies your feature branch against the explicit base branch first, ensuring safe integration before presenting any merge or PR completion options.

You should keep a git branch as-is when you are not ready to finalize changes. This completion option pauses the workflow, preserving your current feature work locally without merging, creating a pull request, or triggering cleanup steps.