finishing-a-development-branch

To finalize a git feature branch after tests pass, you can use a structured workflow that presents four explicit options: merge, pull request, keep, or discard. It enforces test verification first, then executes the chosen action along with optional worktree cleanup.

The options for finalizing a git worktree within this flow are explicitly limited to four choices: merge into the base branch, create a pull request, keep the branch, or discard the work. Post-cleanup and worktree management are performed after selecting an option.

No, you cannot merge a development branch if tests are failing. This structured workflow implements a strict guard that prevents merges and pull requests when tests fail, enforcing test verification before offering any integration actions.

The best way to standardize a pull request and merge workflow is to enforce a fixed decision process. This approach determines the base branch, presents four explicit options after tests pass, executes the chosen action, and performs structured post-merge cleanup for clear developer handoff.

You do not need a specific CI pipeline setup, but you need a git-based workflow where tests can be verified locally or through CI before finalization. The process supports collaborative handoff to developers, reviewers, and CI pipelines after integration.