Repository Settings - Separate repo size limits for Git vs LFS objects

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

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.