-
Notifications
You must be signed in to change notification settings - Fork 17
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
Integrate antsibull-docutils into CI and build scripts and instructions #309
Conversation
I've marked this back to ready for review since it's needed for ansible-community/antsibull-changelog#174. |
I'll try to get to this later today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks! If the plan is for antsibull-docs to directly utilize code for antsibull-docutils, we should also add a direct dependency on it.
I agree. Right now it only uses it indirectly, but if we want to add MarkDown output to antsibull-docs at some point, it will be useful (and then it definitely should become a direct dependency). Or if antsibull-docutils has a RST writer, then we could allow collections to have extra docs in MarkDown. |
@gotmax23 thanks for this one as well! |
Prepares for ansible-community/antsibull-changelog#174.