Component

Forge

Describe the feature you would like

Issue

Currently, when installing a specific version/branch of a dependency, this version is lost when running forge update.
Example:

forge install rari-capital/solmate@v7
forge update

=> checks out to master
I would expect the checked out branch to remain the same.

Example Scenario

I currently am depending on

When the computer is suspended during a fuzzing session, the time spent in suspended state is counted as a "run time" on a statistics screen. In case fuzzing was running for several hours and then the computer was suspended for several more hours, on one hand I would prefer not restarting the session, on the other hand, now it may be harder to tell how well a harness performs (corpus count vs. run

Hello everyone,
I think that the boofuzz documentation is good, but somehow not very useful for beginners.
In my opinion, the quickstart section is too short, leaving new users without any guidance on how to use this framework.
So I would suggest adding a whole section with detailed examples, covering at least the current examples,

I wonder if it was considered to add a rewrite step as a MSBuild target in the NuGet package. This way calling the tool coyote rewrite wouldn't be needed as that would be done automatically once the assembly is generated.

Could possibly be done if a specific property is provided like /p:CoyoteRewrite=true or be an opt-out when Configuration=Debug.