I had troubles trying to use git LFS, despite the many suggestions here on SO, on Git and GitHub's documentation, and on some Gists I'd run across.
My problem was as follows:
After performing the necessary steps:
git lfs install
git lfs track "<file of interest>"
git commit
I would still not have any files being tracked. If I performed
git lfs ls-files
it would be blank. If I went ahead & performed the push, the transaction would fail, saying that the files are too large. (As expected, but I was desperate.)
I then discovered a few fixes, some of which seem to be bugs, some of which simply were not obvious to me.
It seems that in order to use lfs
with an existing repository, a hack or third party tool such as BFG's converter is needed.
git init
, etc.
git remote add origin [email protected]:<my_id>/<my_repo>.git
Also, while Git's Training Video claims that you can simply specify a folder, such as "my_folder/"
, I could not get this to work. Therefore, I just cleverly used filename extensions to manage things.
git lfs track "my_folder/"
would not work for me, but git lfs track "*.zip"
did work.I had no luck getting LFS files to be identified correctly unless I had first updated the .gitattributes
file, and committed and pushed that new file to the remote server.
git lfs track "*.zip"
git add .gitattributes
git commit -m "Updated the attributes"
git push
git add my_large_file.zip
git lfs ls-files
my_large_file.zip
being tracked.git commit -m "Now I am adding the large file"
git push
It's possible that some of the things work, and I was simply doing them wrong. However, following the witchcraft described above finally got LFS to work, so I thought I'd pass on these details for others, in case someone else had the same problem.