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
1. Not Gitmodules **doesn't require to keep the folders** with modules. You can safely .gitignore or delete them.
183
183
2. **Do not use matching names**forthe repositoriesin`notgitmodules.yaml` file. In that case only the first repository
184
-
will be downloaded and the second one will be skipped.
184
+
will be downloaded and the second one will be skipped.
185
185
3. Not Gitmodules **needs**`Git` and `PyYAML`for functioning.
186
186
4. Not Gitmodules, just like Gitmodules, **doesn't automatically install the dependencies of submodules** _(such as requirements.txt for Python or package.json for JavaScript)_.
187
187
5. Not Gitmodules **doesn't download the sub-dependency submodules** (if they are not defined properly for Git).
188
-
- Reason: it's practically inefficient, may lead to bugs and bottlenecks, and better to maintain manually.
189
-
- Solution: Include the sub-dependency submodule to YAML file manually.
188
+
- Reason: it's practically inefficient, may lead to bugs and bottlenecks, and better to maintain manually.
189
+
- Solution: Include the sub-dependency submodule to YAML file manually.
190
190
6. Not Gitmodules keeps the view of keeping the project structure clean. All submodules among one
191
191
project/microservice need to go to one folder. It's recommended to use dependency injection in case of having nested `not_gitmodules`.
192
-
7. **Possible bottleneck** with private repositories.
192
+
7. **Possible bottleneck** with private repositories.
193
193
- If cloning fails, but you have access to the repository, provide the HTTPS repo URL instead of SSH url in YAML file.
194
-
194
+
8. If your python version is incompatible with `PyYAML==6.0` try to install the compatible version of `PyYAML`.
0 commit comments