finishing-a-development-branch

To complete a development branch, run tests to verify passing, detect your workspace environment state, then select an integration path like merging or a pull request. This structured process guides branch completion while managing cleanup of branches and worktrees.

The best way to manage git branch cleanup after merging involves selecting a cleanup workflow that handles the deletion or preservation of branches and worktrees. This ensures efficient integration while maintaining quality control over your repository.

Environment detection determines the current workspace state to select the appropriate integration path for your development branch. By checking the environment, it guides whether to merge directly, create a pull request, or keep the branch.

Yes, you can create a pull request directly from the development branch workflow. The process presents clear choices for merging, creating a pull request, or keeping the branch for later integration based on your environment state.

Yes, you need to verify tests before merging a git branch. Test verification ensures all tests pass before presenting integration options, guaranteeing quality control and preventing broken code from entering your repository.