Question: unable to rmdir: Directory not empty

[iegorval]

I have a local copy of a huge repo and I need to keep only a subfolder of a submodule with the related history. It seemed from all description that git-filter-repo is what should do the trick. I run git-filter-repo --path PATH_TO_SUBFOLDER_TO_KEEP --force.

However, first issue is that I am getting warning: unable to rmdir: Directory not empty for all other submodules that should be deleted. How to force this delete? Or some manual update of the git-filter-repo script with eg. rm -r would be required?

Second issue is that not even at PATH_TO_SUBFOLDER_TO_KEEP I see some changes: all files, except a few files on a top-level module, stay in their places. The unmatched submodule files do not get deleted. Or does git-filter-repo delete only related history, and the files themselves are expected to be kept? Or it has troubles with nested submodules?

UPD git filter-repo --analyze also does not list the paths to any files in the submodules.

[puchongcnxx29]

I have a local copy of a huge repo and I need to keep only a subfolder of a submodule with the related history. It seemed from all description that git-filter-repo is what should do the trick. I run git-filter-repo --path PATH_TO_SUBFOLDER_TO_KEEP --force.

However, first issue is that I am getting warning: unable to rmdir: Directory not empty for all other submodules that should be deleted. How to force this delete? Or some manual update of the git-filter-repo script with eg. rm -r would be required?

Second issue is that not even at PATH_TO_SUBFOLDER_TO_KEEP I see some changes: all files, except a few files on a top-level module, stay in their places. The unmatched submodule files do not get deleted. Or does git-filter-repo delete only related history, and the files themselves are expected to be kept? Or it has troubles with nested submodules?