myco:feature-branch-worktree-squash-merge-delivery

Git worktree isolation creates a separate sibling directory for developing non-trivial features spanning multiple files, preventing branch conflicts before a final squash-merge into a single commit.

A squash-merge workflow combines multiple file changes into one commit by running quality gates like a simplify pass and full build before merging the feature branch for a clean PR history.

Use this workflow for non-trivial features that span multiple files and require isolated development, ensuring a disciplined quality gate process and a single-commit PR delivery.

Yes, a structured simplify pass and a full build are required quality gates before the final squash-merge to ensure code quality and reduce the feature changes into a single commit.

Yes, the workflow orchestrates Git worktrees and a squash-merge specifically for non-trivial multi-file changes, ensuring structured isolation before collapsing the history into one commit.

Feature branches accumulate commits during development; a final squash-merge workflow collapses these changes into a single commit before pushing to ensure a clean repository history.