finishing-a-development-branch

To finalize a git development branch after tests pass, you choose from four explicit options: merge locally, push and create a pull request, keep the branch, or discard the work. The workflow detects the base branch and cleans up related worktrees automatically.

The options for finishing a feature branch are merging locally, pushing to create a pull request, keeping the branch active, or discarding the work entirely. This ensures a clear path to integrate changes once implementation and tests are verified.

When merging a completed branch, worktree cleanup is handled automatically during the finalization process. After you select your preferred integration method, the workflow removes the related worktree to keep your working context clean.

Yes, finalizing a development branch requires verified test results before proceeding with integration decisions. The workflow enforces this validation to ensure the feature branch is complete and stable before offering the merge or pull request options.

Yes, you can discard changes instead of merging a finished feature branch. Discarding the work is one of the four explicit choices offered during the branch finalization process, providing a structured way to abandon unwanted implementation.