Describe script arguments in documentation #675
Conversation
This file contains hidden or 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
Signed-off-by: Kenji Brameld <[email protected]>
Signed-off-by: Kenji Brameld <[email protected]>
ijnek
changed the title
Signed-off-by: Kenji Brameld <[email protected]>
Signed-off-by: Kenji Brameld <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Simply describes the argument parsers for all scripts on the RTD page. A lot of the details are (only) described in bloom/Tutorials/FirstTimeRelease, but it'd be better to have the arguments described here. (and using autogeneration). This also reduces the amount of detail covered in the FirstTimeRelease tutorial.
This PR simply sets up the documentation to display the script arguments, and makes no attempt at cleaning up the current arguments so that they display nicely in the docs. I (or someone else) should clean up the docstrings so they display nicely on RTD in another PR.
Related: ros2/ros2_documentation#2357