Enable LFS setting UI for Masters and Owners
What does this MR do?
Enables the LFS setting UI in projects for Masters and Owners.
The API allows this to be set by Masters (since it is non-destructive) already but in the interface it was limited to Administrators only. This is annoying for users and inconsistent with our approach to permissions which should allow users to self manage and keep admin settings in the /admin
interface.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Disabling LFS is a useful feature for project maintainers to prevent LFS objects if the maintainer doesn't want LFS to be used, and is also needed to disable LFS verification checks if storing LFS objects externally (like a project on GitHub).
Screenshots (if relevant)
Project | Group |
---|---|
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support addedpre-existing -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-and-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #33320 (closed)
Edited by James Ramsay (ex-GitLab)