finishing-a-development-branch

To finalize a git feature branch, you select and execute a merge, pull request, or cleanup workflow. The process verifies tests pass and CI is green, discovers the base branch, and executes the chosen integration action.

Options for merging a development branch include merging locally, pushing to create a PR, keeping the branch, or discarding work. After selecting an option, the workflow executes the action and performs optional worktree cleanup.

Yes, you need to verify CI checks are green and all tests pass before merging a git pull request. The workflow ensures test suites pass and CI status is confirmed before presenting structured options to consolidate changes.

The best way to clean up git worktrees after merging is to select a completion option that executes optional cleanup. The workflow removes worktrees and feature branches as needed after the chosen merge or PR action completes.

Yes, you can use this workflow to discard work on a git development branch. Discarding work is one of the structured completion options presented after verifying tests and determining the base branch.

You should keep a git feature branch instead of merging when implementation needs further review. The workflow presents keeping the branch as a deterministic completion option alongside merging, creating a PR, or discarding work.