It feels like you have one repo even though there are actually two and one of them can be shared across many projects. If this is a library that you are developing, you can make the modifications in the project that uses the library, and then push to the repo of the library! This is the biggest selling point to me because it means that you can, in one place, work on the library and the project that uses it.You always know which version of the library you are using: it is written in the Git submodule.Adding a new submodule is fairly straightforward. It is easier to update: you simply have to pull from the original repository If it doesn't, you may need to run git clone with the -recursive flag, which will scan and update all submodules. Adding -recursive is only required if any submodule itself has submodules.I didnt see a -recursive flag for subtree. Doing git submodule update pulls/updates the submodules but it changes to the wrong branch even when the branch I want to ALWAYS use is specified in the. Then, another developer who wants to have submoduledirectory changed to that tag, does this. I want to pull/update the submodules at the right branch. git add submoduledirectory git commit -m 'moved submodule to v1.0' git push.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |