Skip to content

Checking existing advisories should consume one API request #13

@pinkforest

Description

@pinkforest

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions