docs(config): explain network selection - #2052
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
figtracer
marked this pull request as ready for review
August 29, 2026 16:37
figtracer
requested review from
figtracer,
mablr,
mattsse and
stevencartavia
as code owners
August 29, 2026 16:37
mattsse
approved these changes
Aug 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a user-facing network configuration guide that distinguishes compiled support from runtime selection and explains configuration, CLI overrides, fork inference, namespaced hardforks, Celo, and legacy selectors. It also links the guide from the network reference and Anvil forking documentation.
Companion to foundry-rs/foundry#16430 and addresses the user-facing documentation gap tracked in foundry-rs/foundry#16248.
AI assistance was used to audit current Foundry behavior, draft the guide, and validate the rendered site.
Prompted by: fig