lfx-test-journey

Multi-repo feature journey testing coordinates feature branches from multiple git repositories into isolated worktrees under ~/.lfx-journeys. It merges selected branches into journey-specific directories for end-to-end validation without altering your original branches.

Yes, git worktrees isolate multi-repo integration environments by creating journey-specific directories under ~/.lfx-journeys. This allows you to merge branches from multiple repositories into isolated worktrees for end-to-end testing without modifying the original branches.

Cross-repo feature validation workflows are managed through interactive gates that guide repo discovery, branch selection, and journey naming. You can create, refresh, edit, and teardown isolated integration environments using standard git commands and user prompts.

Refreshing a multi-repo worktree uses the refresh flow to re-merge selected branches from latest HEADs into the existing journey directory. This updates your isolated integration environment under ~/.lfx-journeys without requiring a full teardown and recreation.

No, multi-repo journey testing does not alter your original git branches. It uses git worktrees to merge selected feature branches into isolated directories under ~/.lfx-journeys, keeping the original repository branches completely untouched during end-to-end validation.

You should teardown an integration testing worktree when the end-to-end journey testing is complete or the environment is no longer needed. The teardown flow removes the journey-specific directory under ~/.lfx-journeys and cleans up the associated merged worktrees.