Best practices for tracking a repository with Git submodules and worktrees in gortex

[flojud]

Hi everyone,

I’m setting up gortex for a repository structure that uses both Git submodules and Git worktrees, and I'm looking for some guidance on the correct configuration/workflow.

• Repository structure: My main repository contains 3 Git submodules.
• Requirement: I do not want to track or index the submodules independently as separate codebases; I want them treated purely as part of the parent workspace context.
• Workflow: I heavily rely on Git worktrees for parallel development branches.
• Current status: Running gortex project points correctly to the parent Git repository.

Whenever I work inside a linked worktree, I run into indexing and routing issues:
The daemon logs are flooded with errors like checkout coordinator reconcile failed, for every worktree we have. The workspace's route stays pending with ready=false. Queries consistently fall back to the base graph with:fallback_reason: view_building

How should I correctly configure gortex to track a parent repository with submodules when working across multiple worktrees?

Any advice, examples, or best practices for this setup would be greatly appreciated! Thanks in a lot for your help.