<!--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=352997) </details> <!--IssueSummary end--> ### Problem to solve In GitLab, we would like to encourage developers not to commit non-code data into the repository if it's not an LFS object. With LFS objects, the data can be stored in a cheap object store like S3. With normal Git objects, I don't think this is possible. Currently, there's only a single maximium repo size setting, which includes both normal Git objects and LFS objects. ### Proposal Have separate limit settings for standard Git objects and Git LFS objects. ### Intended users * Any persona which might need to commit large files into Git, such as test data, designs, etc.