docs: Task outputs clarifications #9185
Merged
Conversation
This file contains 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
To avoid the impression that cache is disabled when `outputs` key is ommitted. `API reference` was more accurate for that behavior, than `Crafting your repository`.
turbo-orchestrator
bot
added
area: docs
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 6 Skipped Deployments
|
|
@boutchitos is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
boutchitos
commented
Sep 26, 2024
boutchitos
commented
Sep 26, 2024
boutchitos
commented
Sep 26, 2024
anthonyshew
requested changes
Sep 26, 2024
boutchitos
force-pushed
the
outputs-docs-clarifications
branch
from
436cef2
to
95a88cc
Compare
|
@anthonyshew: I applied your suggestions! |
anthonyshew
approved these changes
Sep 28, 2024
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.
To avoid the impression that cache is disabled when Task
outputskey is ommitted.API referencewas more accurate for that behavior, thanCrafting your repository.Description
I'm new to Turborepo, and was reading Crafting your repository. Two sections lead me to conclude that when there is no
outputskey in a Task, then caching is disabled. I think the wording inAPI referenceis better.We have to account for Logs output even if there are no file outputs (which is really nice for linters).
Testing Instructions