You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gh-openapi-docs tool is being used by several Cloud WS specifications (DRS, WES). It automatically builds documentation and pushes it to the website (ie. gh-pages branch) at a URL path that is based on the github branch name. We could use this in RNAget to streamline the previewing of features, as well as for new releases.
I set this tool up for DRS and would be good to set it up here if we're interested. The current page structure we have in gh-pages is modelled on how the tool writes new files/directories for new docs.
Hi @jb-adams,
It sounds like a good idea as it would make docs more uniform across different GA4GH "products". In my opinion it is definitely worth setting it up for RNAget.
If we go for it, just let me know if you need anything from my side.
The gh-openapi-docs tool is being used by several Cloud WS specifications (DRS, WES). It automatically builds documentation and pushes it to the website (ie. gh-pages branch) at a URL path that is based on the github branch name. We could use this in RNAget to streamline the previewing of features, as well as for new releases.
I set this tool up for DRS and would be good to set it up here if we're interested. The current page structure we have in gh-pages is modelled on how the tool writes new files/directories for new docs.
@saupchurch @emi80 WDYT? Is this worth setting up for RNAget?
The text was updated successfully, but these errors were encountered: