finishing-a-development-branch

To safely merge a git feature branch, the workflow requires running the project's test suite first, halting if tests fail, then choosing to merge locally, push and open a pull request, keep the branch, or discard it with typed confirmation.

Cleaning up git worktrees when discarding a branch requires detecting associated worktrees, removing them when appropriate, and requiring typed confirmation before executing destructive branch deletions to prevent accidental data loss.

Yes, you can open a pull request directly from your local git workflow by selecting the push and create a PR option after verifying passing tests, which pushes the branch and generates a structured PR body for the target codebase.

To determine the correct base branch before integrating a development branch, the workflow automatically detects the merge-base to identify the target codebase branch, ensuring the feature integration applies to the correct repository lineage.

Running tests before merging a development branch is required to prevent integrating broken code, as the workflow mandates executing the project's test suite and halts the integration process immediately if any tests fail.

Yes, the branch integration workflow supports keeping a branch for later work by offering a structured decision flow that allows developers to preserve the current development branch instead of merging, pushing, or discarding it.