Aditya Agarwal

@anwersayeed do you want me create an entirely new project and test as I was doing the testing and integration in talawa-docs repo.

@anwersayeed here is the script : #!/bin/bash git clone --depth=1 --branch automated-docs https://github.com/adi790uu/talawa-api.git mkdir -p docs/talawa-api-docs cp -r talawa-api/talawa-api-docs/* docs/talawa-api-docs/ rm -rf talawa-api ls git config --global user.email "[email protected]" git...

> @anwersayeed here is the script : #!/bin/bash > > git clone --depth=1 --branch automated-docs https://github.com/adi790uu/talawa-api.git > > mkdir -p docs/talawa-api-docs > > cp -r talawa-api/talawa-api-docs/* docs/talawa-api-docs/ > > rm...

we can extend this for talawa-admin as well.

@anwersayeed the workflow is working in case there are changes in talawa-api-docs and pushing it to develop branch in talawa-docs

this is the version of script used : #!/bin/bash git clone --depth=1 --branch automated-docs https://github.com/adi790uu/talawa-api.git mkdir -p docs/talawa-api-docs cp -r talawa-api/talawa-api-docs/* docs/talawa-api-docs/ rm -rf talawa-api git config --global user.email "[email protected]"...

what change need to made here as I am using my credentials: git config --global user.email "[email protected]" git config --global user.name "adi790uu"

similarly we can clone mobile and admin repos add the doc folders to talawa-doc and push them to develop.

@Cioppolo14 it will fail as I have removed certain parts of the workflow which are not necessary after the merge of my latest PR in talawa-docs repo

@anwersayeed can you review this.