-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use consistent documentation generation directories/names to support matrix actions from cFS #2083
Comments
skliper
added a commit
to skliper/cFE
that referenced
this issue
Apr 11, 2022
skliper
added a commit
to skliper/cFE
that referenced
this issue
Apr 11, 2022
This was referenced Apr 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Naming isn't consistent, osal-apiguide uses osalguide directory, mission-doc generates a detaildesign directory but the warning file gets put in the docs directory instead of subdir, etc.
Describe the solution you'd like
Make behavior consistent.
Describe alternatives you've considered
None
Additional context
Cleaning up top level nasa/cFS#447
Requester Info
Jacob Hageman - NASA/GSFC
The text was updated successfully, but these errors were encountered: