Repository navigation
Replies: 1 comment
|
This overlaps with #22664, which asks for the same cross-environment grouping for non-git folders but solves it with an automatic folder-name fallback instead of explicit linking. Use cases there include a multi-repo parent folder and non-dev work in synced folders. Explicit linking seems like the safer of the two, since it can't group unrelated folders that share a name. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Related: #7838 (treating multiple machines as one workspace). This is one concrete, narrow slice of it.
Problem
Some of my projects span several repos, so I keep one folder per project that holds all of them, plus local notes and screenshots:
I add the parent folder as the T3 project and run one long-lived thread there. It works across all the repos and opens PRs in whichever one the task needs. The same folder exists on my laptop and on a remote devbox.
The sidebar merges projects across environments only by git remote (
repositoryGroupingKeyOf). A folder that isn't a repo falls back to a key of environment plus path, so I get two separate entries for the same project. To follow one piece of work I either switch between them, or pick "All projects" and wade through threads from every unrelated project.Proposal
Let the user link projects on different environments as one project (e.g. "Link with project on …" in the project menu), stored as a client-side grouping override like
sidebarProjectGroupingOverrides. The merged entry then behaves like any multi-environment repo project: one thread list and an environment choice for new threads. Unlinking reverses it. No server or sync changes.Relation to #10500
This is the root cause behind my comment on project multi-select (#10500 (comment)). Linking would cover my main case on its own, since filtering to the one linked project hides everything else. Multi-select would stay useful for viewing genuinely different projects together, but if you'd only take one of the two, this is the one I'd pick.
Workaround today
git initplus an identicaloriginremote in each copy, which works but fakes a repo identity just for grouping.@t3dotgg @juliusmarminge would you accept this scope? If so, I'll send one focused PR (web and mobile, with before/after screenshots) linking your reply.
All reactions