Git-lfs: Git still pushing big file

Created on 23 Jan 2017  路  3Comments  路  Source: git-lfs/git-lfs

Hi,

I'm using Ubuntu 16.04. I have an issue I can't quite understand. The git lfs already sent de two files to the lfs server. However, git seems to continue to send the big files to the repo. Leaving the same issue as before I installed lfs.

git push origin master
Username for 'https://github.com': ***  
Password for 'https://***@github.com': 
Username for 'https://github.com':***
Password for 'https://***@github.com': 
Git LFS: (0 of 0 files, 2 skipped) 0 B / 0 B, 209.17 MB skipped                
D茅compte des objets: 24, fait.
Delta compression using up to 4 threads.
Compression des objets: 100% (21/21), fait.
脡criture des objets: 100% (24/24), 99.02 MiB | 1.25 MiB/s, fait.
Total 24 (delta 3), reused 0 (delta 0)
remote: Resolving deltas: 100% (3/3), done.
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
remote: error: Trace: 80a9999bd1b4ccaaf8c0ed4d22b40e68
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File drone.stl is 197.97 MB; this exceeds GitHub's file size limit of 100.00 MB
To https://github.com/***/***.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: impossible de pousser des r茅f茅rences vers 'https://github.com/***/***.git'

When I do git lfs ls-files

My files are followed as I wanted.

2bb20c3350 * drone.stl
185290d15b * test.stl

Most helpful comment

HI @MaxiMax07, a little bit of an update. Since you've opened this, Git LFS has started shipping with the git lfs migrate command, which can help you easily remove large files from your repository's history. You can give this a shot with:

$ git lfs migrate import --include=path/to/file
# ...

Please let me know if you have any issues!

All 3 comments

Your repository still has drone.stl in the git history, even if a more recent commit used LFS. I think the easiest thing would be to roll things back to the version on github, and then re-apply the changes as a single squashed commit. Let me know if you need help with that.

One thing we could do going forward to address this issue is teach lfs ls-files to warn about situations like these, though I'm not sure if we can do that quickly without maintaining a local cache.

Maybe git lfs ls-files --warn-untracked or similar?

HI @MaxiMax07, a little bit of an update. Since you've opened this, Git LFS has started shipping with the git lfs migrate command, which can help you easily remove large files from your repository's history. You can give this a shot with:

$ git lfs migrate import --include=path/to/file
# ...

Please let me know if you have any issues!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

danielbayley picture danielbayley  路  4Comments

pointcache picture pointcache  路  4Comments

vtchalakov picture vtchalakov  路  4Comments

panpan0000 picture panpan0000  路  3Comments

m1h4 picture m1h4  路  4Comments