If you've used git+LFS for any extended period of times, you'd know how often it breaks, especially when used with forges like GitHub. Both GitHub and Git treat LFS as an after-thought and second class citizen.
If you've used git+LFS for any extended period of times, you'd know how often it breaks, especially when used with forges like GitHub. Both GitHub and Git treat LFS as an after-thought and second class citizen.
Can you tell me where did it break? Or what feature you wished it had? I’m just curious, still trying to form an opinion on this.
I searched through my browser history to see what issues I googled the last time I used it, here is a non-exhaustive list:
- Auth errors with github because of different supports for various methods which results in the unhelpful "does not support the locking API error"
- Encountered files that should have been pointers but weren't errors
- Github handling the spec wrong such that file pointers that are invalid can make it through to Github such as multiple file pointers to the same file, but that have different line endings (issue 5410 on the git-lfs github if you want to see the details)
- Semi-frequent object does not exist on the server errors
- LFS support cannot be used on forks in github (you must instead manually clone the project and upload as un-related)
- Cloning with non-default ssh key is somewhat convoluted (issues 2842 2215 2727 4145 and 2433 on git-lfs)
Some of these are actual git-lfs issues which make using the usual git API break such as the auth/ssh-key stuff, whilst others are simply that it is much easier to get yourself into a bad state with git-lfs than vanilla git. Of course you can always get yourself out of a bad state by fresh-clone, or forcing etc.... but with large files this becomes a non-instant operation.