Guidance for PR Reviews with large cache changes

[dannyrb]

👋 Hello,

I'm using the Zero Install feature, but it is making pull request reviews difficult for our team. Is anyone else butting up against this issue? Is there an easy fix/workaround that we're not aware of?

1. Install one or more packages as a part of a new feature
2. Check in the .yarn/ changes
3. Cache changes overwhelm/hide the one or two files that would normally be reviewed

If there is a better place to ask, any help to point me in the right direction would be appreciated 🙏

[noahnu]

You can filter out the zip files using File filter in github.

[osdiab]

filtering htem out just collapses them, but the individual file entries still get rendered, which usually means there's still hundreds of cache files to scroll past. And if there are too many cache files, even the file navigation box says that it has too many files, so doesn't work. it sucks - but i don't really see a better way besides not committing them until after code review, or making a separate branch that just contains the yarn cache updates, without intervention from Github to make it better.

[osdiab]

I experience the same thing, commenting to bump this if anyone has any good suggestions. I suspect (as in the other comment I wrote here) that it's not really great until Github makes some edits to their UI, though.