finishing-a-development-branch

To finalize a git development branch, you can use a structured workflow that verifies tests pass, detects the base branch, and presents four explicit options: merge locally, push and create a pull request, keep the branch as-is, or discard it entirely.

Yes, you can create a pull request from a git worktree and trigger automatic worktree cleanup. The workflow pushes your changes, creates the PR, and then handles local and remote worktree removal post-completion.

The best way to ensure tests pass before a local git branch merge is to use an automated test verification step. This enforces test-driven completion by blocking the merge action until all tests successfully pass.

To safely discard a git branch and remove its worktree, you can select the discard option from a structured finish flow. This enforces safeguards to prevent unsafe actions while cleaning up the local and remote worktree.

Yes, the branch finishing workflow automatically detects the appropriate base branch for merging. This ensures your local merge or pull request targets the correct parent branch without manual configuration errors.