-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Repository Vulnerability Alert Missing Fields #1897
Comments
Thank you, @OhZedTee ! What is the difference between I couldn't get your "docs" URL link above to work. |
I've updated the link, thank you. I don't see a clear difference, in my testing they seem to have the same value but I did notice the Github API add these new fields. Not sure if they plan to deprecate one or the other, but since I was checking for missing fields in the Repository Vulnerability Alert, I noticed this as well. In the doc, you'll see the fields in the example Webhook payload right before the sender object. |
Weird! If you feel like it, it might be nice to contact GitHub tech support and ask them what the differences are between these fields... If you do that, feel free to report back here as to the differences. Thank you! |
Good idea, I'll get in touch. EDIT: I've opened a support ticket with them to get clarity. |
Hi @gmlewis, I've received a response from GitHub. This is what they had to say verbatim:
So maybe it's best to add the deprecated field because it's currently there to stay, however, the new field is open_issues_count. |
OK, awesome, @OhZedTee ! Something like: // Deprecated: OldField old description goes here.
OldField *string `...` |
Sure, I can do that once this PR and Issue are closed. Would you like a separate associated Issue with that PR? Or is the PR enough? |
Just a new PR would be fantastic... you can refer to this issue (probably closed by then) in the description as a reference. Thank you, @OhZedTee ! |
Alternatively, you could add the changes to #1898... I'm fine either way... your call. |
Struct for repository_vulnerability_alert webhook event is missing fields that are mentioned in docs.
These fields need to be added to the struct, and tested.
The fields are:
alert.severity
alert.created_at
alert.ghsa_id
repository.watchers
repository.open_issues
The new structs should like as such (I used to show what should be added):
event_types.go
repos.go
I don't mind performing the code change if you could assign this issue to me.
The text was updated successfully, but these errors were encountered: