Skip to content
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

Open
palisadoes opened this issue Jan 10, 2025 · 12 comments
Open

NoMongo: Restore the GraphQL Introspection GitHub Action Test #3235

palisadoes opened this issue Jan 10, 2025 · 12 comments
Assignees
Labels
bug Something isn't working test Testing application

Comments

@palisadoes
Copy link
Contributor

Describe the bug

  1. Now that we have started the migration from mongodb to postgres, we need to reenable our GitHub actions introspection test to make it pass.
  2. This may potentially break the app. Issues will need to be created accordingly after this PR is merged.

Expected behavior

  1. Restore the functionality to .github/workflows/pull-request.yml by uncommenting the section in the image below
  2. Make the tests pass and if that is not possible coordinate with @noman2002 and @rishav-jha-mech

Actual behavior

  • Disabled

Screenshots

image

Additional details

  • N/A

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@raggettii
Copy link
Contributor

@palisadoes please assign this to me

@palisadoes
Copy link
Contributor Author

@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.

@raggettii
Copy link
Contributor

@palisadoes Although i have made the changes and tests were running and was about to create a PR

@raggettii
Copy link
Contributor

@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.

@palisadoes
Copy link
Contributor Author

@raggettii have you started working on this? I'm concerned that you have two important issues that could stall progress of our postgres migration.

@raggettii
Copy link
Contributor

@palisadoes I have already started working on the issues. Will create a PR for the same ASAP

Copy link

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.

@github-actions github-actions bot added the no-issue-activity No issue activity label Jan 21, 2025
@palisadoes
Copy link
Contributor Author

Unassigning. Inactivity

@github-actions github-actions bot removed the no-issue-activity No issue activity label Jan 21, 2025
@Priyanshuthapliyal2005
Copy link

@palisadoes can you assign this issue to me

@Priyanshuthapliyal2005
Copy link

I have started working on this issue.

@hustlernik
Copy link
Contributor

@Priyanshuthapliyal2005 Do you need any help, if possible let us collab.

@Priyanshuthapliyal2005
Copy link

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working test Testing application
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

4 participants