finishing-a-development-branch

Finalizing a Git development branch involves verifying tests pass, then choosing to merge locally, push and create a pull request, keep the branch, or discard it. This structured workflow ensures safe integration and worktree cleanup.

Finishing a feature branch merge offers four fixed options: merge locally, push and create a pull request, keep the branch for continued work, or discard the branch entirely. This guides integration decisions across common Git workflows.

Cleaning up a Git worktree after completing a feature branch happens automatically once you select an integration action. The workflow safely removes the worktree after a local merge or discard, or preserves it when keeping the branch.

Creating a pull request instead of merging a Git branch locally depends on your team workflow. The workflow presents both options alongside keeping or discarding the branch, letting you choose push and PR for collaborative review or local merge for direct integration.

You can discard a development branch safely after tests pass by selecting the discard option in the workflow. This safely removes the branch and cleans up the associated worktree without forcing a merge or pull request.