Goals

Allow remote caching to be disabled for specific task only

Non-goals

No response

Background

Some local development tasks are specific to a developer's repository only, but should only be ran once. With remote caching once one of the developer in a team run that task for a current input, the next developer running the task will hit the cache even though the output of the operation that will be performed cannot really be cached.

Proposal

Have a task level property in turbo.json for enabling/disabling remote caching.