-
Notifications
You must be signed in to change notification settings - Fork 43
Open
Labels
Status: Up for grabsIssues that are ready to be worked on by anyoneIssues that are ready to be worked on by anyoneType: BugSomething isn't working as documentedSomething isn't working as documented
Description
What happened?
Currently $.pull_request.{base,head}.repo
in Pull Request-related events (e.g. pull_request reopened event
) is marked as #/definitions/repository
, which has a mandatory custom_properties
field.
It is a mistake because in GitHub docs, pull_request
events do not have such a field there. And this schema will not pass validation with a strict validator.
It is strange because #900 reported the opposite behavior recently. I suppose there might have been an API regression from GitHub side.
Here is an example payload.
Versions
@octokit/[email protected]
with octokit-rs
.
Relevant log output
`Error("missing field `custom_properties`", line: 195, column: 17)`
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
Status: Up for grabsIssues that are ready to be worked on by anyoneIssues that are ready to be worked on by anyoneType: BugSomething isn't working as documentedSomething isn't working as documented
Type
Projects
Status
🔥 Backlog