finishing-a-development-branch

To finalize a development branch after CI tests pass, you verify the green test results, determine the correct base branch, and select from four structured finish options to merge or discard the work.

The best way to merge a feature branch or create a pull request is to use a deterministic workflow that detects your base branch and presents explicit finish options, ensuring you choose the correct integration path.

Branch cleanup after merging involves executing the chosen finish action and then performing end-to-end worktree maintenance to safely remove the completed feature branch from your local environment.

Yes, you can keep a development branch as-is by selecting the corresponding finish option, which pauses the merge process while preserving your current work without triggering local merge or pull request actions.

Ensuring CI tests are green before finishing a git workflow branch requires a verification step that checks test results, preventing any final merge or pull request actions until the CI passes.

You should discard work on a feature branch instead of merging when the feature is no longer needed, utilizing the discard finish option to remove the work and execute proper branch cleanup.