<!--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=343200) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal `git-lfs` mentions in its [FAQ](https://github.com/git-lfs/git-lfs/wiki/FAQ) a way to set up a flow where one can text-based diff LFS stored/tracked files. I think it would be great if GitLab could support diffing files that are tracked with `diff=lfstext` in the `.gitattributes` file. `lfstext` is just a convention mentioned in the FAQ, and a developer can define a custom global converter with any name. However, I think just tracking this convention and supporting text-based diffing of certain LFS files would be very helpful. <!-- 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. -->