What problem does git subtree solve?
When and why should I use that feature?
I\'ve read that it is used for repository separation. But why would I not j
Basically Git-subtree are the alternatives for the Git-submodule approach: There are many drawbacks or rather I would say, you need to be very careful while using git-submodules. e.g when you have "one" repo and inside "one" you have added another repo called "two" using submodules. Things you need to take care:
When you change something in "two", you need to commit and push inside "two", if you are at top-level directory (i.e in "one") your changes wont get highlighted.
When an unknown user tries to clone your "one" repo, after cloning "one" that user needs to update the submodules to get the "two" repo
These are some of the points and for better understanding I would recommend you to watch this video: https://www.youtube.com/watch?v=UQvXst5I41I
To overcome such problems subtree approach is invented. To get the basics about git-subtree, have a view on this: https://www.youtube.com/watch?v=t3Qhon7burE
I find subtree approach is more reliable and practical compare to submodules :) (I am very much beginner to say these things)
Cheers!