Better CLI error when LFS is not enabled
Problem to solve
When pushing LFS changes to a project without LFS enabled, you get this error (even as owner of the project)
Took me QUITE some time to figure out what went wrong.
Proposal
Make GitLab return something more clear like LFS is not enabled or Your changes include LFS objects, but you are not allowed to use LFS in this project or something of the like
What does success look like, and how can we measure that?
- Create a project, disable LFS
- Add LFS objects to your local checkout of the project
- Commit and run
git push - GitLab returns a more usable error message than the above.