docs: clarify passthrough args comparison #10990
Merged
Conversation
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
## Description The current docs for global hash inputs made me think that _any_ passthrough arg would invalidate the cache when present. Stupid, I know. But I read it several times and just could not parse the meaning correctly. The suggested fix would hopefully make it clear that the different examples are compared to the output of the first command.
Contributor
|
@emilbjorklund is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
anthonyshew
approved these changes
Oct 17, 2025
Contributor
anthonyshew
left a comment
There was a problem hiding this comment.
Makes sense! Thank you.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Description
The current docs for global hash inputs made me think that any passthrough arg would invalidate the cache when present. Stupid, I know. But I read it several times and just could not parse the meaning correctly.
The suggested fix would hopefully make it clear that the different examples are compared to the output of the first command.