I'm having issues with github desktop, spewing the 'Files too large' warning when trying to commit, even though I ran the Git LFS configuration already. In total, there are 11 files causing this issue and they're all in the same folder.
I installed Git LFS and added the problematic folder to the git lfs track with git bash, as described here, but instead of associating a file type, I associated the problematic folder directory.
After having done this, and verifying that the .gitattributes file is indeed changed, I tried to commit my pending changelist with github desktop again.
The problem: I'm still getting the warning from GitHub Desktop, saying that Files are too large, with a suggestion that I should use Git LFS instead.
How do I solve this?
but instead of associating a file type, I associated the problematic folder directory
I suggest you don't do that, as it is clearly stated:
To associate a file type in your repository with Git LFS, enter git lfs track followed by the name of the file extension you want to automatically upload to Git LFS. source
run instead git lfs track '<problematic folder>/*.dll'
. Indeed, .gitattributes
do not, by default, track nested folders recursively - as suggested in issue #3963.
The rules by which the pattern matches paths are the same as in .gitignore files (see gitignore[5]), with a few exceptions:
negative patterns are forbidden
patterns that match a directory do not recursively match paths inside that directory (so using the trailing-slash path/ syntax is pointless in an attributes file; use path/** instead) source
See also issue #2214