You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.
Pretty new to Foundry so go easy on me here if I'm just missing something obvious.
But Foundry isn't initializing dependencies with this readme and not with forge install either. From what I can find in the forge documentation it should use the submodules to install dependancies in lib/ once forge install is called. And these are defined in .gitmodules. I can copy paste the data in there 1 by 1 and get it installed. But I imagine the issue here is that if you use forge init --force and you do need to use the force flag, then a new lib/ folder is created without the submodules even though they're defined in the root folder.
May need to publish the project post forge-init to be cloned with the submodules, or if that's too crowded include a script to
for module in submodules:
forge install module.url
The text was updated successfully, but these errors were encountered:
Pretty new to Foundry so go easy on me here if I'm just missing something obvious.
But Foundry isn't initializing dependencies with this readme and not with
forge install
either. From what I can find in the forge documentation it should use the submodules to install dependancies in lib/ once forge install is called. And these are defined in .gitmodules. I can copy paste the data in there 1 by 1 and get it installed. But I imagine the issue here is that if you useforge init --force
and you do need to use the force flag, then a new lib/ folder is created without the submodules even though they're defined in the root folder.May need to publish the project post forge-init to be cloned with the submodules, or if that's too crowded include a script to
The text was updated successfully, but these errors were encountered: