-
-
Notifications
You must be signed in to change notification settings - Fork 803
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
Update documentation workflow #968
Conversation
Our Pull Request Approval ProcessWe have these basic policies to make the approval process smoother for our volunteer team. Testing Your CodePlease make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:
The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing. ReviewersWhen your PR has been assigned reviewers contact them to get your code reviewed and approved via:
Reviewing Your CodeYour reviewer(s) will have the following roles:
CONTRIBUTING.mdRead our CONTRIBUTING.md file. Most importantly:
Other
|
@anwersayeed @tasneemkoushar Please review |
This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work. |
@anwersayeed @tasneemkoushar Should we close this? |
This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work. |
@anwersayeed @tasneemkoushar Should this be closed or should it be merged? |
This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work. |
@anwersayeed @tasneemkoushar Should this be closed ?? |
This one changes the token name but as the Talawa Admin docs were failing previously, maybe this was the PR that we missed merging. |
@Nitya-Pasrija Can you fix the failing tests for this so that we can get it workflow operational? It does not look like a lot of work. |
We may close this for now. |
@anwersayeed There is no issue for this PR Please create an issue for this so that we can track it, then close this PR. |
Sure, I'm looking into this one |
@Nitya-Pasrija This is causing the Talawa-Admin documentation to be missing from docs.talawa.io. How is your progress? |
@Nitya-Pasrija This is causing the Talawa-Admin documentation to be missing from docs.talawa.io.
|
@Nitya-Pasrija any progress on this PR? |
I have started looking into it, will resolve it max to max by first week of December |
@Nitya-Pasrija Are you still on track to complete this by next week? |
@Nitya-Pasrija Are you still on track to complete this? |
Yep. I'll be creating a PR by Sunday evening |
7b2b238
to
5a475c8
Compare
@Nitya-Pasrija Why was this closed? |
A recent PR 968 on Talawa docs, has created major changes and resolves the linking errors as well. Thus, it would have created confusion to have two different PRs referencing different workflows |
@Nitya-Pasrija there is no PR 968. What is the PR you are referencing? |
There is ons under the talawa-docs repository, cuz of the version updates the workflows were activated and hence, they are all working out now. |
Do you mean this PR? And if so, is everything working in the documentation workflow for Talawa Admin and Talawa API? |
No description provided.