Many moons ago I added a subtree to my git
repository. This subtree included several folders and files. I added the subtree instead of creating a submodule (as recommended). Now I realize I only want one of the files in the subtree and none of the rest. Even worse, when others clone
my repository, what they get is not what is expected—there is some conflict with the subtree and the other code that I've created.
I can get ride of the files/folders with
git rm subtree–folder1 subtree_folder2 subtree_files.*
however, I'm still left with a lengthy commit history from the subtree.
I've done a fair amount of development since I originally added the subtree and can't lose the commit history that I've generated.
In short this is what I would like:
Is this possible?
PS. One possible complication is that I moved the single header file I wanted to keep from the subtree to some folder in my code. I hope this is not what is keeping me from forgetting the subtree history.
After a fresh checkout from the remote server I have the following:
$ ls .git CMakeLists.txt Read.cpp logging.conf .gitignore ENDF6 TestData src .sparse-checkout LICENCE doc test .travis.yml README.md include tools
Where .gitignore
only has: build/ debug/
When I try the command as suggested I don't get a very happy response:
$ git filter-branch --index-filter 'git rm --cached -rf test tools src doc LICENCE README.md .travis.yml' HEAD Rewrite 2fec85e41e40ae18efd1b130f55b14166a422c7f (1/1701)fatal: pathspec 'test' did not match any files index filter failed: git rm --cached -rf test tools src doc LICENCE README.md .travis.yml
I'm not sure why it says it has a problem with test
when it is clearly there. I'm baffled.
No, git rm (plus the commit) writes a new tree that reflects the file is no longer present. The entire history of the file, including creation, modifications, and eventual deletion, is present in the history.
Splitting the Original Repository The subtree commands effectively take a folder and split to another repository. Everything you want in the subtree repo will need to be in the same folder.
You need to use a filter-branch along with the --prune-empty option to remove any commits that no longer introduce new changes.
git filter-branch --index-filter 'git rm --cached --ignore-unmatch -rf dir1 dir2 dirN file1 file2 fileN' --prune-empty -f HEAD
After that, if you want to recover disk space you will need to delete all the original refs that filter branch saved, expire the reflog, and garbage collect.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With