GitHub Community
Problem with a jar file stored with Git LFS extension #21900
-
|
Hi, I have an issue with a jar file that I stored with Git LFS on this repo. When I git clone the repo with git clone line command the downloaded jar file is corrupted. When I download it from the Github GUI here it works perfectly. The dowloaded files seems to be different since sha fingerprints doesn’t match 3ea6457e99d217caaf152e240c3c6795aeb32eea from the corrupted file I get when I git clone the repo and e471c7bc25368311899993224ce3635f4eb6307e from the file I get from the GUI. Could you explain me if this is a known issue with jar files stored with Git LFS or if I did something wrong when I first push it to my GitHub repo ? Regards, David |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
I solved my issue, just had to reinstall git lfs on my new machine and run git lfs pull on my local repo just as stated here. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dgoncalvesramos, Just FYI, this post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information. As you’ll notice, your Topic is now in the How to use Git and GitHub board. Thank you for updating the Topic with the solution once you discovered it! Cheers! |
Beta Was this translation helpful? Give feedback.
I solved my issue, just had to reinstall git lfs on my new machine and run git lfs pull on my local repo just as stated here.