Issue with git lfs #123294
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I was using git lfs for the first time and I think I made a mistake using this tool. I was working on a local feature branch. I ran following on this branch:
and I kept working on this branch for many days and accumulated many commits. When the feature was code complete, I started an interactive rebase to squash my changes into 1 commit:
This is when I got an error. The log has this message:
It is true this object does not exist on the server. I am not sure if it is my mistake but it shouldn't be trying to download an object that has not been pushed in the first place. I somehow managed to continue with the rebase. I don't remember the exact steps I followed but most likely I did a combination of:
.gitignore
to ignore the large files being tracked by git lfsgit config lfs.allowincompletepush true
after this I was able to push to my remote on github. but now I cannot push the lfs file no matter what I do. I keep getting errors:
how can I fix this?
when I see something like:
does it mean the contents of
.git
are identical across my local and remote? what is the way out? do I have to contact someone in GitHub?Beta Was this translation helpful? Give feedback.
All reactions