You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, if the subtree is merged and then updated, this command that is supposed to update the local subtree fails with a fatal: refusing to merge unrelated histories error.
Hey, this is the issue tracker for the git-scm.com website, not Git itself. If you still want to discuss this issue, you should reach out to the community.
Yeah, --allow-unrelated-histories didn't exist when v1 of the book was published. If the issue persists in v2, I'd suggest opening an issue on the progit/progit2 repo. For general discussion of squash strategies, try the community link that @sxlijin pointed to.
Following the instructions here:
https://git-scm.com/book/en/v1/Git-Tools-Subtree-Merging
will lead to an error.
In particular, if the subtree is merged and then updated, this command that is supposed to update the local subtree fails with a
fatal: refusing to merge unrelated histories
error.A workaround could be using the
--allow-unrelated-histories
optionBut this completely destroys my project by pushing the subtree contents into a completely irrelevant directory in my project (no in the subtree).
Any ideas??
The text was updated successfully, but these errors were encountered: