Closed bryceschober closed 1 day ago
Have you tried completely uninstalling LFS, doing the merge, and reinstalling afterwards? I just tried it locally with your example and it seems to work here.
As I understand it LFS is "transparent" to bare git (using smudge filters) and you don't actually have to instantiate anything. In fact it will probably be a lot faster :) then do a git lfs update
when you're done.
Yep, I think you're right, and for the record for any others setting GIT_LFS_SKIP_SMUDGE=1
is probably the easiest way to disable LFS smudging operations while using this tool.
So, with this testmono.repos.txt
:
https://github.com/hraban/tomono.git tomono tools/tomono
https://github.com/Apress/repo-with-large-file-storage.git lfsrepo
...This sequence of commands resulted in the desired behavior:
$ env MONOREPO_NAME=testmono GIT_LFS_SKIP_SMUDGE=1 ./tomono/tomono < testmono.repos.txt
$ git lfs fetch --all lfsrepo
I wonder what it would take to support LFS, or if that's too big a lift for the plumbing involved...
Here's my public test case:
testmono.repos.txt
:I have already install git lfs globally, so that I can just
git clone
from my own repos using LFS and everything "just works":But when I run
tomono
, I get: