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

[Schema Inaccuracy] Missing pull_request dequeued reason enum #3838

Open
thejcannon opened this issue Aug 9, 2024 · 3 comments
Open

[Schema Inaccuracy] Missing pull_request dequeued reason enum #3838

thejcannon opened this issue Aug 9, 2024 · 3 comments

Comments

@thejcannon
Copy link

Schema Inaccuracy

The reason for pull_request dequeued is marked a string, but is some enum. It'd be nice to know the values.

Expected

An enum.

Reproduction Steps

N/A

@sachigoyal
Copy link

Hi @thejcannon
Before:
The code is trying to use the enum that is not defined , not imported or any other reason.
After:
In this Issue we need to change the "reason" field data type from string to an enum. Along with changing its data type we need to include specific values like:
"merged"
"closed"
"head_ref_deleted"
"automatic_head_ref_deleted"
"other"
Thankyou

@bearcherian
Copy link
Contributor

@thejcannon Thanks for filling this issue. Can you point to the API spec or documentation file where you are seeing this? Is this a webhook or an API endpoint that you are working with?

@thejcannon
Copy link
Author

I see it here in the OpenAPI spec for one. But also here: https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=dequeued#pull_request

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

No branches or pull requests

3 participants