finishing-a-development-branch

To finish a git feature branch, the workflow verifies CI test results, identifies the base branch, presents completion options like merging or creating a PR, and cleans up the worktree and branch automatically.

The best way to merge a development branch after CI testing passes is to select a fixed completion option. You can merge locally, push and create a pull request, keep the branch as-is, or discard the work entirely.

Yes, you can create a pull request or discard local changes when finishing a branch. The workflow provides exact completion options: merge locally, push and create a PR, preserve the branch, or discard the work.

Yes, finishing a branch verifies test results before merging. The workflow ensures the feature branch passes the CI test suite prior to finalizing, preventing untested code from reaching the base branch.

To clean up git worktrees after completing a feature branch merge, the workflow performs automatic cleanup of worktrees and branches after your chosen completion action executes, ensuring no residual artifacts remain.

You should preserve a git feature branch instead of merging when work is incomplete or needs review. The workflow allows keeping the branch as-is, bypassing merge or PR actions while maintaining the worktree state.