finishing-a-development-branch

To finish a development branch after tests pass, you choose from four explicit wrap-up options: merge locally, push and create a PR, keep the branch for later, or discard the work. This enforces pre-merge validation to ensure code quality.

The best way to wrap up a Git feature branch is to validate tests and determine the base branch before finalization. This coordinates with common Git workflows and CI to guide you through selecting the appropriate cleanup or merge action.

Yes, this workflow supports creating a pull request after CI completes. It offers structured post-CI wrap-up options, allowing you to push your work and create a PR directly once the pre-merge test validation passes.

To determine the base branch for a Git merge, the workflow suggests the appropriate target branch during the finalization process. This ensures your development work merges into the correct integration line after tests pass.

Yes, you can discard your Git branch changes instead of merging them. The workflow provides an explicit action to discard the work, ensuring clean history if the feature is no longer needed or fails requirements.