LFS limitations

[MontoreDeFinesko]

Select Topic Area

Question

Body

Hello, I created a new repository and uploaded an Unreal Engine project to it. My colleague cloned my repository, and everything was fine. We checked to see if changes were being made to the repository from both his and my side, and everything was successful. But today, after working in Unreal Engine, I did a git push, after which my colleague tried to download my changes, and he received this error. How can I fix it?

[Ranjuna120]

Commit or stash local changes before pulling, using this

git add .
git commit -m "Save local changes"
git pull
or
git stash
git pull
git stash pop

[MontoreDeFinesko]

The error mentions something about the lfs limit.

[Ranjuna120]

Try pulling with rebase

git pull --rebase

[MontoreDeFinesko]

If I buy a girhub pro subscription, will this error go away?

[Ranjuna120]

Yes, then you can easily fix errors.

[Ranjuna120]

Clean untracked files (be careful, this deletes uncommitted files

git clean -fd
git pull

[Ranjuna120]

try step by step

[MontoreDeFinesko]

We've done everything according to your instructions.

[Schuylerzheng]

1 LFS Merge error which I don't know about, and one is because you don't have enough LFS bandwidth I think
(bandwidth article: https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage)

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬