finishing-a-development-branch

To finalize a git development branch, you enforce test success as a gate and select a structured integration option: merge locally, push and create a PR, keep the branch, or discard the work.

The best way to merge a feature branch safely is to detect the base branch, run tests to gate integration, and choose an explicit lifecycle action like a local merge or PR to finalize the work.

To manage git worktree lifecycle when discarding a feature branch, the workflow handles the worktree cleanup and requires explicit discard confirmation before removing the completed or abandoned work.

Yes, you can create a pull request by selecting the push and PR option after the test suite passes the gating check and the base branch is detected for the development branch.

The four options for integrating a completed development branch are merging locally, pushing to create a PR, keeping the branch active, or discarding the work with explicit confirmation.

You should gate branch merges with test success to ensure complete work passes tests before integration, preventing risky merges and ensuring only validated code reaches the base branch.