-
Notifications
You must be signed in to change notification settings - Fork 190
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
Automate rest api docs generation #4168
Conversation
84f5737
to
0e0f8cc
Compare
112141c
to
4a725bc
Compare
9ab8922
to
c62a0a2
Compare
3f0ff02
to
387f0b7
Compare
387f0b7
to
86d5f79
Compare
86d5f79
to
0d3196f
Compare
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.
I love this, and we (read: me, probably) should think about extending this to other APIs when possible.
I have some blocking feedback, especially around details of the PR that gets opened. I also started some conversations in my feedback, and we should not hesitate in those conversations to qualify things as worthy of follow-up PRs instead of blocking this one.
The image used for our GH runners contains nvm, likely we are using an older version of nvm not available in the runner
Hey @pepopowitz @akeller I addressed all the suggestions, please have another look 😄 |
a61cbcd
to
31d557c
Compare
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.
This looks great, thanks for making changes!!
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.
👍 No complaints!
This PR add a GH workflow to automate the creation of REST API specification in our documentation