Elijah Newren
Elijah Newren
Cool, glad you found a solution to handle your case of migrating out of LFS. I suspect filter-repo could still make things better (e.g. does git lfs update referenced sha1sums...
Actually, I think I'll change my mind and close this one out just to keep the issue list tidy. I've got it marked with the contrib-candidate label though to help...
Very interesting problem. I'm not sure how to create a repository that duplicates this. The only way I could imagine this triggering is if one commit was output multiple times...
Here's a simple way to reproduce that triggers the problem for me: ``` #!/bin/bash rm -rf stupid git init stupid cd stupid seq 1 10 >numbers git add numbers git...
See contrib/filter-repo-demos/clean-ignore in this repository; it'll clean all of history based on the gitignore rules from HEAD. I think that does exactly what you want?
Yep, sounds like a bug. Thanks for the report and the clear steps on how to trigger.
Wow, that looks bad! I don't have time at the moment to investigate, but thanks for reporting. I'll try to look at it soon.
Can you report the output of `git remote -v` after running, and the git-filter-repo command line you used?
Are you using --partial, --refs, --source, or --target by chance?
Ah, yeah, good catch. It bases on whether there are refs/remotes/origin/* refs to rewrite, which there won't be for a mirror clone. Updating the docs would be good.