seal

Automating feature branch finalization involves verifying tests, determining the base branch, presenting four completion options, and cleaning up git worktrees. This ensures a deterministic and auditable conclusion to feature development.

To prevent merging code when tests fail, enforce a workflow that runs tests across common frameworks and halts automatically upon failure, guaranteeing bad code is never integrated into the base branch.

Yes, this branch management workflow supports npm test, cargo test, pytest, and go test. It automatically detects and runs the appropriate test framework to verify code before finalizing the branch.

To clean up git worktrees after completing a feature branch, use an automated finalization workflow that removes residual artifacts and worktrees automatically once a chosen completion path is executed, keeping repositories tidy.

When finalizing a git feature branch, you have four explicit options: merge locally, push and create a pull request, keep as-is, or discard. This standardizes branch completion and ensures deterministic behavior.