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.

Sign up for GitHub

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

Jump to bottom

Checking existing advisories should consume one API request #13

Open

pinkforest opened this issue Apr 4, 2023 · 0 comments

pinkforest commented Apr 4, 2023

We are also consuming API query per advisory when checking if one already exists which is sub-optimal

This is due to using the REST API

Check if with GraphQL via octokit we could reduce this to one query

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment