subdirectory-filter corrupting repository with nested directory named like its parent about git-filter-repo HOT 9 CLOSED

Thanks for the report. This could be a duplicate of issues #3 and #35 ; even though the flags are a bit different the underlying bug could cause this issue here too. Those two bugs have workarounds listed in them, but more importantly, I pushed up a fix for the underlying issue on Christmas and am just awaiting confirmation from others that it fixes their problem before closing out those issues.

What version of filter-repo are you using? Does it include the fixes I pushed two days ago, by chance? If the latest version of filter-repo doesn't fix your problem, an example repo would be very helpful.

from git-filter-repo.

from git-filter-repo.

Thanks for trying out the latest version. I'm scratching my head trying to figure out what else might cause this, so an example repo would be very helpful.

from git-filter-repo.

As for now, my attempt to reproduce the error in a smaller repo failed, though I found another strange behaviour - this time reproducible I hope (see #38). I'll get back to this one in a few days when I have more time.

from git-filter-repo.

Thanks for trying to come up with a smaller testcase. I tried a couple simple example repos that matched your structure as well, but none of them worked for me to reproduce either. I'll await your further investigations (or you could just give me access to your real repo & steps to reproduce, so long as it's something you're allowed to have me take a look at).

from git-filter-repo.

Sorry for taking so long to answer.
I cannot grant you access to the repo as it is corporate one.
Meanwhile preparation of the test case is of low priority unfortunately, but I do hope to get back to it soon-ish. For now, thanks to explanations from #24 (which did happen in my case too), I was able to work around the issue.

My workaround was changing repositories I am exporting, thus not needing to export this specific path. Not really applicable for others probably :-)

from git-filter-repo.

Well, I'm glad the fixes for #24 helped you out at least. I understand shifting priorities; I'll leave this open for now and hope you get a chance to find some steps to reproduce at some point and pass them along.

from git-filter-repo.

May possibly have been caused by #53, in which case this should be fixed. Any chance you could retest?

from git-filter-repo.

Rather than leave this open forever, and since it may likely have been caused by #53, I'm going to go ahead and close. Do let me know, though, if you're able to reproduce with a version with #53 fixed and/or come up with any steps for duplicating this problem.

from git-filter-repo.