Indicate in merge requests when files changes LFS status
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=433125) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal If a LFS-tracked file is (deliberately) modified and (accidentially) removed from LFS in the same commit, it is not clearly visible in the merge request that the LFS status was changed. The changed files section will say "The source diff could not be displayed because it is stored in LFS.", even if only the original file is in LFS. The careful MR reviewer can see that the line count increases dramitically due to LFS-removal, but it is too easy to miss. Suggests to add a clear indication in the MR Changes section when existing files are added to or removed from LFS. ![image](/uploads/b10f43aa37a7d016a648063ac80cdadd/image.png) <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->
issue