-
Notifications
You must be signed in to change notification settings - Fork 21
error: failed to push some refs to 'github.com:langdon/my-private-repo.git' #14
Comments
I'm not working on this anymore but it should still work. You should be able to get more info about the failure by setting |
Did you find a solution to your problem @langdon ? |
Sorry, should have been clearer:
|
Okay thanks, new to git here, and I'm desperately trying to set an LFS system, Gits default storage is way too small and I can't pay monthly for storage |
For me it was a path with spaces in it. There is a note in the Readme - so it was a RTFM problem. Solution: add extra single quotes to add the path to your folder: See also: #4 |
Hi, thanks for writing this software. After reading and following all instructions, I was still getting the "failed to push some refs ..." error. So adding the single quote around my google drive path (g:/My Drive/) didn't resolve the problem. However, I did some more digging. After asking some questions on Chat-GTP, I found my issue. Turns out git bash on Windows, which is the environment where I am doing my git source control stuff, couldn't call the command lfs-folderstore.exe during git push because it doesn't recognize it. Running the 'GIT_TRACE=2 git push' helped me track down the source of this issue. Btw, looks like adding lfs-folderstore to my Windows environmental variable doesn't work on git bash. To finally solve my problem, I added "export PATH=$PATH:/c/path/to/lfs-folderstore/" to my ~/.bashrc config file. Now git bash is able to call the lfs-folderstore.exe and I am able to do proper git push with lfs assets in my commits to my google drive. Yay! Hope this shed more light on the issue for anyone who might still be struggling to get this to work. |
I am not sure if you are maintaining this anymore but it could be super helpful for all of my CSVs for doing data science work.
However, I am running in to
I am running on linux and have tried existing and new repos with no luck.
Any ideas?
The text was updated successfully, but these errors were encountered: