Upable to mirror repos with large file sizes.

[trevski]

Description

When mirroring I get the following error due to 2 large files in my repo

remote: error: See https://gh.io/lfs for more information.
remote: error: File packages/Magick.NET-Q8-AnyCPU.11.1.0/Magick.NET-Q8-AnyCPU.11.1.0.nupkg is 101.53 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: File packages/Magick.NET-Q8-AnyCPU.12.1.0/Magick.NET-Q8-AnyCPU.12.1.0.nupkg is 101.38 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com./

Value

To enable repos with large file sizes to be mirrored.

[calebcartwright]

It's not conclusively clear from the issue description, but my impression is that you are trying to mirror from something to GitHub.

If that's indeed the case then the first question we have to rule out is whether you've enabled LFS on your target repo in GitHub? The error message seems pretty clearly to stem from the hosting provider, and there's not really anything we can do on our end (the extension simply runs a few git commands, but doesn't directly deal with the provider platforms)

[charnv]

I am having the same issue except the files it's complaining about are no longer in my repo. How do I sort that out? I assume it's using files that are cached/retained but I have run "git rm --cached -r" & double checked the repo. I also set the retention to 1 day for my pipeline artifacts etc. but still get the same error, over and over and over.

Errors:
remote: warning: File xxx/.next/cache/webpack/client-development/20.pack is 89.39 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB
2023-07-21T13:11:54.3877978Z remote: warning: File xxx/.next/cache/webpack/client-development/20.pack is 89.35 MB; this is larger than GitHub's recommended maximum file size of 50.00 MB

These files literally do not exist.

Additional context: I am running this in an AzureDevOps release mirroring an AzureDevOps repo to a GitHub repo.

Any suggestions?