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
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,13 +27,14 @@ your project.
27
27
28
28
## Important note
29
29
30
-
1. not_gitmodules just like Gitmodules doesn't `automatically install the dependencies`/`do not include the dependencies to your project dependency file` of the submodule.
30
+
1. not_gitmodules just like Gitmodules doesn't `automatically install the dependencies`/`do not include the dependencies to your project dependency file (such as requirements.txt for Python or package.json for JavaScript)` of the submodule.
31
31
2. not_gitmodules doesn't `download the submodules mentioned in the not_gimodules.yaml file of the submodule`.
32
32
- Reason: it's practically inefficient, may lead to bugs and bottlenecks, and better to maintain manually.
33
33
34
34
How to handle?
35
-
1. Move the containing of the dependency file to your project.
36
-
2. Move submodules to your `not_gimodules.yaml` file and rerun install accordingly.
35
+
1. Move the containing of the dependency file to your project's dependency file and rerun the dependency installer.
36
+
2.1. Important note. `not_gitmodules` keeps the view of keeping the project structure clean. All submodules amoung one project/micro-service need to go to one folder. It's recommended to use dependency injection in case of having nested not_gitmodules.
37
+
2.2. Move submodules to your `not_gimodules.yaml` file and rerun install accordingly.
0 commit comments