git subtree does not add new metadata files like git submodule does (i.e.They can ignore the fact that you are using git subtree to manage dependencies. git subtree does not require users of your repository to learn anything new.The sub-project’s code is available right after the clone of the super project is done.Older version of Git are supported (even older than v1.5.2).Management of a simple workflow is easy.It is one of several ways Git projects can manage project dependencies. Git subtree lets you nest one repository inside another as a sub-directory. What is git subtree, and why should I use it? In this post we will look at git subtree and show why it is an improvement – albeit not perfect – over git submodule. While submodules are useful for a few use cases, they do have several drawbacks.Īre there alternatives? The answer is: yes! There are (at least) two tools that can help track the history of software dependencies in your project while allowing you to keep using Git:

The Internet is full of articles on why you shouldn’t use Git submodules.

Unity cloud build submodules folder