Minimise some diffs in a merge request

Description

Some files like npm-shrinkwrap.json and yarn.lock are not that useful when making a new merge request and make the diff really big. This can slow down the code review process.

Proposal

I propose to have some sort of way to that will make it possible for developers to say what files should be in a minimised state.

It could be automatic, we know already that npm-shrinkwrap.json and yarn.lock files contain a lot of lines and can have a lot of lines changed but the information the diff has is not at all useful (since the changes are already in the package.json file).

Or, maybe have a file that has the same semantics as the .gitignore file where the developers can list the files that they don't want to be visible right away in a merge request.

Cheers.