feat(`forge`): avoid repulling in dependencies when using git worktree

[colin-morpho]

Component

Forge

Describe the feature you would like

I often find myself in the following situation.
I work on a new feature for repo r so I:

$ cd r
$ git worktree add -b new-feature-a features/new-feature-a
$ cd features/new-feature-a
$ git submodule sync
$ foundry i

This process is annoying because I have to sync submodules and install dependencies which is often long, instead I would expect dependencies to be shared across worktrees, or at least cached.

Additional context

No response

[IronJam11]

Can I work on this issue

[grandizzy]

@colin-morpho this doesn't seem like something to be implemented on forge side, we could think at adding a local cache registry, is that what you're referring to?

[colin-morpho]

@grandizzy tbh, I haven't really thought about the problem or the solution. I figure that a simple trick would involve remappings and looking at the git file and the source repo of a worktree, could that do the trick? The idea would be to remap dependencies at the main git repo. Which can be inferred from the git file of the worktree, maybe the user still has to run forge i but it would set up a remapping instead of pulling dependencies all over again.