git:git-submodules
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
git:git-submodules [2023/05/02 16:34] – admin | git:git-submodules [2023/05/07 19:26] (current) – admin | ||
---|---|---|---|
Line 21: | Line 21: | ||
</ | </ | ||
- | Information on submodules can be found in **.gitmodules** and **.git/ | + | Information on submodules can be found in **.gitmodules** and **.git/ |
+ | |||
+ | If we add the changes, commit and push , the content of submodules will not been added in the main project git, but information on how to retrieve it will be stored. In our example we push the changes : | ||
+ | <code bash> | ||
+ | git add --all | ||
+ | git commit -m "add python_control_coppeliasim external git repo" | ||
+ | git push | ||
+ | </ | ||
+ | |||
+ | In another computer we can simply clone the main project repo and we will see that there is nothing in the submodule. The content of the submodules can be pulled by | ||
+ | <code bash> | ||
+ | git clone <git URL> | ||
+ | cd <git repo main folder> | ||
+ | git submodule update --init | ||
+ | </ | ||
+ | If we know when cloning the main project git that there are submodules we can pull them at the start with **--recursive** keyword: | ||
+ | <code bash> | ||
+ | git clone <git URL> --recursive | ||
+ | </ |
git/git-submodules.1683038073.txt.gz · Last modified: 2023/05/02 16:34 by admin