finishing-a-development-branch

Finishing a development branch involves validating tests, choosing a merge or PR path, and cleaning up worktrees. You can execute a local merge, push to create a PR, keep the branch, or discard work, all with guarded cleanup procedures.

Cleaning up git worktrees after merging is handled by guarded cleanup procedures that activate once you select a closure option. This ensures a clean Git history by safely removing temporary work artifacts after the integration decision.

Yes, you can choose between a local merge and a pull request. The workflow provides four explicit options for finalizing a branch, allowing you to select a local merge or push to create a PR based on your project's collaborative needs.

To discard git branch changes safely, select the discard option within the branch closure workflow. This triggers guarded cleanup procedures that remove the specific branch and worktree, ensuring unrelated repository work remains completely unaffected.

The branch merge workflow relies on standard Git commands and CI feedback to verify tests pass before proceeding. You should activate the workflow after all tests pass to ensure integration decisions are made on validated code.