Skip to content
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

Closed
skliper opened this issue Apr 11, 2022 · 0 comments · Fixed by #2085 or #2091
Closed
Labels
docs This change only affects documentation. draco-rc2
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Apr 11, 2022

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

@skliper skliper added the docs This change only affects documentation. label Apr 11, 2022
@skliper skliper added this to the Draco milestone Apr 11, 2022
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
astrogeco added a commit that referenced this issue Apr 18, 2022
Fix #2083, Fix #2086, Consistent doxygen flow/naming for generation and use reusable documentation generation workflow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change only affects documentation. draco-rc2
Projects
None yet
1 participant