git-subtree pull complications
We have been trying to get git-subtree working on a project (with git version 1.7.9.4) and have run into a bit of a complication. Someone else previous added the subtree with this command some months ago:
git subtree add --prefix=foo [email protected]:foo.git master
Now there have been substantive changes to foo and we'd like to merge in those changes, ideally squashing them in. None of the files have been modified since they were imported.
I've tried three things to try and merge in the changes.
First:
git subtree pull --squash -P foo [email protected]:foo.git master
Which throws the exception: Can't squash-merge: 'foo' was never added.
Second:
git subtree pull -P foo [email protected]:foo.git master
This works (sort of), but has the issue of pulling in all of the commits and has conflicts with the files that have been modified.
Finally, I tried this:
git pull --squash -s subtree [email protected]:foo.git master
This gives me the desired result, with the output Automatic merge went well; stopped before committing as requested and all of the files showing up as modified (with the correct content).
Ideally I'd like to continue using first git-subtree version and get an output close to the last version. If we have to use the last version consistently going forward, we will, but I am a little confused as to why the last one doesn't produce merge conflicts while the middle one does.
Any help is appreciated.
Answer
I had the same problem, and in my case it seems to be due to the initial subtree commit being merge-squashed into the master branch.
Looking through the subtree source I found this: https://github.com/git/git/blob/master/contrib/subtree/git-subtree.sh#L224
It looks like subtree greps your git log for git-subtree-dir: foo but doesn't find a suitable commit. Try git log --grep="git-subtree-dir: foo/*\$", and if there's something weird with that commit, such as it being a merge commit, that could be the issue.
Just pulling without squashing worked for me, apart from the annoying merge conflicts. I did that in a temporary branch which I then git merge --squashed into another branch to avoid a messier history. It could've been rebased instead too of course.