paths-from-file keeping unrelated files about git-filter-repo HOT 4 CLOSED

I suspect this is a duplicate of #3. If you run with --prune-empty=never, does it get the correct file contents (even if it leaves a lot of ugly empty commits around)?

from git-filter-repo.

I believe you are right.

One thing though: running with --prune-empty=never also left an empty unrelated folder. Strangely enough, this folder wasn't there in my previous attempts, using prune empty.

Running twice with pruning on, like they mentioned on #3, seems to fix it.

After running with --prune-empty=never, is there a way to run a second time just to remove the empty commits? It feels like a better option than running the bugged way twice.

By the way, what is considered a "fresh clone"? I'm running filter-repo on repos that I just cloned but it keeps requiring --force.

I cloned filter-repo today, so I'm using latest. I'm not running it on master.

from git-filter-repo.

I think the changes I just pushed up should fix this issue; could you try the newest version of the master branch and report whether it corrects the problems for you?

from git-filter-repo.

It seems to be working with the repo I have and the test one they posted on #3. Thank you!
I'll test further after 6/Jan.

from git-filter-repo.