-1

I try to push a branch onto a new remote on github. I have an error doing that, stating that some files size are above 100MB. Here's the full log:

$ git push -u perso NewInput
Uploading LFS objects: 100% (393/393), 3.2 GB | 0 B/s, done.
Enumerating objects: 2776, done.
Counting objects: 100% (2776/2776), done.
Delta compression using up to 16 threads
Compressing objects: 100% (2770/2770), done.
Writing objects: 100% (2776/2776), 583.28 MiB | 12.29 MiB/s, done.
Total 2776 (delta 1611), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (1611/1611), done.
remote: warning: File Assets/IfcImporter/Resources/GVH_UV_AR_BIM_Model Architectuur_xml.xml is 80.79 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: warning: File Assets/Scenes/DebugScene/LightingData.asset is 54.35 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
remote: error: Trace: 43af452cf91044eb10637a3dc8c93cb30ecb2e67d5bbdcafe50eed7a91348db0
remote: error: See https://gh.io/lfs for more information.
remote: error: File Assets/IFCImports/GVH_UV_AR_BIM_Model Architectuur.prefab is 129.03 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: File Assets/Scenes/GVH_UV_AR_BIM_Model Architectuur.ifc is 173.53 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
To https://github.com/ArnaudBBRI/CaveBckp
! [remote rejected] NewInput -> NewInput (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/ArnaudBBRI/CaveBckp'

Now, these files used to be tracked, but they are not anymore. So, why is this happening, and how do I solve that? The message also says to try Git Large File Storage, which I am using as far as I know (I did 'git lfs install', and the .gitattributes file has a line for ifc files, for instance: '*.ifc lfs').

Thanks a lot,

Arnaud

Arnaud
  • 445
  • 4
  • 18
  • 1
    Did you commit the files before "untracking" them? – Caleb Aug 18 '23 at 13:08
  • They were added and committed in some previous commit, yes, if that's what you mean? – Arnaud Aug 18 '23 at 13:15
  • https://stackoverflow.com/search?q=%5Bgit-lfs%5D+large+file – phd Aug 18 '23 at 13:29
  • Run `git lfs migrate import` to process commits that already have large files. See https://github.com/git-lfs/git-lfs/wiki/Tutorial#migrating-existing-repository-data-to-lfs – phd Aug 18 '23 at 13:29
  • https://stackoverflow.com/search?q=%5Bgit%5Dremote%3A+warning%3A+file+is+larger+than+GitHub%27s+recommended+maximum+file+size+of+50.00+MB – phd Aug 18 '23 at 13:30
  • Or just remove large files from history if you don't want to track them in the repository. – phd Aug 18 '23 at 13:31
  • 1
    @Arnaud well then, that would be why. You already committed the files so, of course they are going to be pushed. Just undo the commit and make a commit without those files. Problem solved. – Caleb Aug 18 '23 at 13:58

0 Answers0