Removing subtrees? about git-filter-repo HOT 3 CLOSED

Ah, interesting.. your reply got me thinking, and I see what's happening now.

After I git-filter-repo the path containing my subtree, the merge commit for that is rewritten (so it no longer creates files in the subtree path). The child commits for that subtree are still in the repo (and they're not empty, so they're not being removed).

So..I need to make all the subtree history's commits empty as part of this.

from git-filter-repo.

filter-repo by default only removes commits if they become empty; are there other changes that were made as part of those commits that are outside the paths you are removing? You may want to run git log --name-status ... to get a look at some of the commits in question and see which files they still modify. (I'll assume for now that we're not dealing with commits that started empty.) Of course, if you have a complex enough series of merges, then merge commits may need to be retained just to preserve the commit topology. So git log --graph --name-status ... might be handy.

It's hard to say more without getting a chance to look at the repo in question, but hopefully that helps you narrow it down.

from git-filter-repo.

Glad you understand; I'll go ahead and close out.

from git-filter-repo.