Feature: Running `forge update` on unsynced repo should run `forge install`

[sambacha]

trafficstars

Component

Forge

Have you ensured that all of these are up to date?

• [X] Foundry
• [X] Foundryup

What version of Foundry are you on?

No response

What command(s) is the bug in?

No response

Operating System

No response

Describe the bug

Running forge update first when cloning a repo does not ensure that the submodules are synced/checked out.

[onbjerg]

So you want forge update to run forge install and then pull the latest refs?

[shadyalfred]

cli/src/forge.rs Is this where the modifications should go?

[onbjerg]

@shadyalfred Unsure because @sambacha hasn't clarified yet what the behavior should be

@sambacha Ping

[sambacha]

So you want forge update to run forge install and then pull the latest refs?

Sorry just now catching up, yes, it should first install if install successfully then it should update

I can see a reason for it just failing however as well. I think its up to yall do you prefer explicit separation or convenience

[sambacha]

I think this is fixed in the latest release can you confirm @onbjerg ?

at least this behavior is now being done:

$ forge build
Missing dependencies found. Installing now.

[sambacha]

Fixed by #6521 and #6519