add a config option to disallow the cache clean command #6610
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.
What's the problem this PR addresses?
At Datadog we are using
yarn
inside a huge monorepository using the PnP linker and Zero-Installs with all the dependencies versioned through git.The issue we have is that people frequently have the tendency to think that this kind of environment works like others, and that cleaning the cache is the way to go whenever they encounter an install issue (like deleting
node_modules
).This is obviously not the case and we have to tell them to restore their packages from the git remote when that happens, which is a bit cumbersome.
see also: #6518
How did you fix it?
This PR adds a non-breaking option inside the
.yarnrc
file to disallow runningyarn clean cache
.cc @arcanis
Checklist