### Problem Many projects specify a `.gitattributes` file for various settings within their repository. Some of these settings are helpful in providing consistency for [syntax highlighting](https://docs.gitlab.com/ee/user/project/highlighting.html), [line endings](https://git-scm.com/docs/gitattributes#_effects) and other settings when working with a project. While [GitLab supports](https://docs.gitlab.com/ee/user/project/git_attributes.html) these settings in projects, the Web IDE does not read these settings. ### Proposal The Web IDE should systematically load a project's `.gitattributes` file and respect and apply any appropriate settings required during the editing experience. ### Technical Details The backend should provide the `.gitattributes` file to the Web IDE so that the frontend can apply read those settings. There will be an important order of operations aspect when support for the `.editorconfig` is also introduced. For additional details see: https://gitlab.com/gitlab-org/gitlab/issues/22014#note_286457019 <details> <summary>Original Description</summary> GitLab supports setting the `gitlab-language` of a file using the `.gitattributes` file to force the syntax highlighting of blobs. We should also support this in the Web IDE ### Proposal Respect the `gitlab-language` attribute in the `.gitattributes` files ### Links https://docs.gitlab.com/ee/user/project/highlighting.html https://docs.gitlab.com/ee/user/project/web_ide/index.html#comment-3869256360 </details>