finishing-a-development-branch

To finalize a git development branch after tests pass, choose between merging locally, pushing and creating a pull request, keeping the branch, or discarding it. The workflow detects the base branch and guides cleanup to reduce local worktree drift.

Choosing between local merging and creating a pull request depends on your workflow needs after tests pass. A structured workflow presents both as explicit options alongside keeping or discarding the branch, then cleans up the local worktree based on your choice.

Yes, you need to verify tests before merging a development branch. The workflow prompts test verification during end-of-feature work before presenting the four options to merge locally, push a pull request, keep, or discard.

To clean up local worktree clutter after merging a git branch, use the optional cleanup step in the workflow. After selecting a merge, pull request, or discard option, the feature branch is removed to reduce drift and clutter.

You should discard a development branch instead of keeping it when the end-of-feature work is no longer needed. The workflow offers discarding as one of four explicit options, removing the branch and cleaning the worktree to prevent clutter.