-
-
Notifications
You must be signed in to change notification settings - Fork 848
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
NoMongo: Restore the GraphQL Introspection GitHub Action Test #3235
Comments
@palisadoes please assign this to me |
@raggettii I'm going to unassign you from this. In the early stages of the migration we'll need people dedicated to a single issue so that we don't have bottlenecks. Focus on the setup script as that will be extremely useful. |
@palisadoes Although i have made the changes and tests were running and was about to create a PR |
@palisadoes i have made changes and ready to open a PR and also the tests are passing so can you reassign me so that i can open a PR. |
@raggettii have you started working on this? I'm concerned that you have two important issues that could stall progress of our postgres migration. |
@palisadoes I have already started working on the issues. Will create a PR for the same ASAP |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Unassigning. Inactivity |
@palisadoes can you assign this issue to me |
I have started working on this issue. |
@Priyanshuthapliyal2005 Do you need any help, if possible let us collab. |
Sure! I’ve almost finished the first PR assigned to me, and now I’ll start working on this one. Let’s collaborate if possible! |
Describe the bug
Expected behavior
Actual behavior
Screenshots
Additional details
Potential internship candidates
Please read this if you are planning to apply for a Palisadoes Foundation internship
The text was updated successfully, but these errors were encountered: