[ELITERT-1219] Export requirements with the docs #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Requires #19 to be merged for the verifiers to pass. |
Updates the Github action that generates the Sphinx documentation to also include a step to export the requirements as RST. For this the 'dim_to_rst' gem is being added to the development dependencies.
sergio-bobillier
force-pushed
the
sb-export-requirements
branch
from
84a386c to
f6f1515
Compare
albertoberto
approved these changes
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the Github action that generates the Sphinx documentation to also include a step to export the requirements as RST.
For this the
dim_to_rstgem is being added to the development dependencies.