Open diarmidmackenzie opened 1 year ago
Turns out I can disable the LFS settings on my fork of the repo, and now I can clone it fine.
https://github.com/diarmidmackenzie/moonrider/commit/a2fbd32497214562c9ba57b2fe8ebd7f12132832
Maybe there is some downside to this solution, but all seems OK so far...
yeah. I think you should be fine without LFS
I have to investigate what LFS bandwidth quota exactly means. This repo is not cloned a lot. gh-pages traffic perhaps count towards the quota.
Try to clone my fork of this repo, I get the following error:
Retry doesn't work. Following the failed operation, I am left with source code downloaded, but the version history is all messed up and hence I'm not able to commit changes.
The cause of the error seems to be a problem with the parent repo (supermedium/moonrider), not my fork: https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage
"Bandwidth and storage usage only count against the repository owner's quotas. In forks, bandwidth and storage usage count against the root of the repository network. Anyone with write access to a repository can push files to Git LFS without affecting their personal bandwidth and storage quotas or purchasing data packs. Forking and pulling a repository counts against the parent repository's bandwidth limit."
I don't understand why the repo woud be using LFS, as the asset causing the problem is only 604 KB.
Can it be fixed not to use LFS?
I'd like to be able to clone the repo to work further on performance investigations as per https://github.com/diarmidmackenzie/moonrider/issues/3