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
Hello, my organization uses the submodule approach for creating modules. We utilize GitHub Actions workflows to generate README files for each module. However, only the parent modules are currently documented. For instance, in the following example, a README is only created for the 'iam' module, not for its child modules.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, my organization uses the submodule approach for creating modules. We utilize GitHub Actions workflows to generate README files for each module. However, only the parent modules are currently documented. For instance, in the following example, a README is only created for the 'iam' module, not for its child modules.
modules
├── iam
│ ├── cloudfront-stack
│ ├── cloudwatch-rum-stack
│ ├── cognito-stack
│ ├── laravel-stack
│ ├── robot-stack
│ ├── s3-app
│ ├── serverless-stack
How can I create README files for the submodules as well?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions