Allow using LFS if Repository feature is disabled
Summary
When disabling the Repository
feature in the project settings, the LFS
feature is also force-disabled:
What is the current bug behavior?
LFS is disabled, which also breaks the Design Management feature because it uses LFS exclusively for storage.
What is the expected correct behavior?
LFS should still be enabled, Design Management should still work.
Output of checks
This bug happens on GitLab.com
Possible fixes
Not sure if this can be fixed entirely on the frontend by moving the LFS toggle to the top-level.
We should check that the backend doesn't have any coupling between these settings.