Repository navigation
feat: Remove unneeded fork parameter - #361
Merged
Merged
Conversation
keeganwitt
force-pushed
the
remove-fork-parameter
branch
from
February 12, 2026 06:07
f4e461e to
35ed2c7
Compare
keeganwitt
force-pushed
the
remove-fork-parameter
branch
from
February 28, 2026 05:07
35ed2c7 to
7070f7c
Compare
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
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.
Originally, the
forkparameter was added to allow users to opt-into using a forked process even if there were no toolchains present. I now think this isn't a use case that likely makes sense and having the parameter likely just causes confusion (indeed, I even messed up the integration tests).