Repository navigation
Replies: 3 comments
|
I hit this limitation too on T3 Code 0.1.7, using a Mac laptop and a Dell worker running Linux in WSL2. My Mac project is a workspace with this layout: I want to register the corresponding workspace on Dell, select An explicit way to link the two existing project registrations would solve this for me, without making the parent folder a Git repository. I can arrange file transfer separately; the missing piece is one logical project with a machine selector. Explicit linking also avoids accidentally merging unrelated folders with the same name. I found #23531 proposing a shared |
|
I would love to see this as I use T3 Code for a lot of non-dev work that mainly involves non-git directories... |
|
Another non-dev use case, adding detail to the comment above. I use T3 Code for lots of non-code work like research notes, coursework, writing, and personal admin, since it has the best user experience. Each project is a plain folder synced by Syncthing between a Windows laptop and a Linux VM, at The Either shape would cover me. My folder names match across machines, so the folder-name fallback proposed here would work. The explicit linking proposed in #24728 is smaller, though (client-side only), and can't merge unrelated folders that happen to share a name. #23531 tried a server-side version (a stored grouping identity, plus CLI and MCP tools) but was closed as out of scope. |
Uh oh!
There was an error while loading. Please reload this page.
Project grouping keys strictly on git remote URL (
RepositoryIdentityResolver→deriveRepositoryScopedKeyinprojectGrouping.ts, falling back to the per-machine physical key whenrepositoryIdentityis null).A project whose workspace root is a plain folder of repos (no
.gitat the root, e.g. a microservices folder with 20+ services each having their own remote) can never group across environments — it always shows once per machine in every grouping mode (repository,repository_path,separate).Request: when
repositoryIdentityis null, fall back to a normalized key (e.g. folder name or relative path) so same-named folders group into one project with per-machine checkouts.All reactions