Multi repo tasks

[barbaldo]

Are there plan to support multi repo tasks? For example say you have the classic FE / BE repo setup as separate repositories. It would be very handy to be able to manage them as a single task with coordinated worktrees / PR support and such

[mtalexan]

I'm a little confused why this isn't already supported myself. It's only the most trivially simple cases where you'd ever have only a single git repo, or the niche case where you're working on a monorepo.

Far and away the most common use case for anything that's not entirely trivial is to have multiple git repos. Also, very very few people actually use monorepos since it's only been getting decent support from git for the last few years and requires a massive workflow overhaul to switch to it. It's much more common to have a git repo with submodules in it (which cannot be used with git worktrees, trying can actually corrupt the state of the original clone and all worktrees if you try to use them together). There are also a lot of non-standard solutions out there for combining repos in order to work around the significant limitations of submodules, and most of them involve having additional git repos cloned it somewhere within the same workspace.

My point is, it's been well known for many years that:

• git worktrees are rarely an option
• a workspace is almost always multiple git repos

To be fair though, this is an industry-wide problem. Pretty much no tools currently support anything but the most trivially simple workspace, and the common invalid assumptions include git worktrees and single-repo. Emdash at last allows git worktrees to be turned off and custom setup/teardown scripts to be used so it can at least do basic workspace management, even if can't do anything else.