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
Sometimes the RNs are not reviewed as carefully as I would like because it is harder to review Jira fields than a regular PR or MR. I have been using pandoc to create an ODT file, which I convert into a Google doc. Google docs are good for collaboration between stakeholders and writers.
I wrote a GitLab CI job to convert the 'internal.html' file generated by aCoRNs into an ODT file, but the user experience (downloading a zip file of the artifact) is not great. It would be better to integrate the ODT build into aCoRNs, so here is my POC.
The text was updated successfully, but these errors were encountered:
Sometimes the RNs are not reviewed as carefully as I would like because it is harder to review Jira fields than a regular PR or MR. I have been using pandoc to create an ODT file, which I convert into a Google doc. Google docs are good for collaboration between stakeholders and writers.
I wrote a GitLab CI job to convert the 'internal.html' file generated by aCoRNs into an ODT file, but the user experience (downloading a zip file of the artifact) is not great. It would be better to integrate the ODT build into aCoRNs, so here is my POC.
The text was updated successfully, but these errors were encountered: