talawa-api
talawa-api copied to clipboard
CI/CD pipeline for generating JSDoc artifacts used for automating documentation
Following https://github.com/PalisadoesFoundation/talawa-api/issues/474, create a pipeline to run the jsdoc command for any files that get approved in a pull request. After the command has been run, the artifact HTML files generated from this should then be added via a pull request to the path docs/talawa-api/ in the Talawa Docs repo (https://github.com/PalisadoesFoundation/talawa-docs).
Parent Issue:
- https://github.com/PalisadoesFoundation/talawa-docs/issues/188
Sister Issue:
- https://github.com/PalisadoesFoundation/talawa-api/issues/474
i would like to work on this
Is this the correct flow?
Also should we configure this whole action to trigger on push on develop branch, because it only makes sense to update the docs if the code is merged in the develop branch of talawa-api.
@akshatgarg12 Are you still working on this? Did you get a response from @DMills27?
This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.
Hello @akshatgarg12 , I am unassigning you due to no activity.
Is this issue still open for contribution or its been solved?
If it's open can I work on it? I've worked on Github Actions for a while now!
Assigned to you. Now you can work on this.
This issue did not get any activity in the past 14 days and will be closed in 365 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.
@tasneemkoushar should we close this as we are migrating to TSDocs?
unassigned due to inactivity.
Is this issue still open?
Yes, but it should be closed as we are now using TSDocs
@tasneemkoushar Should is there another issue for this for TSDoc? If not, should we create it?