Events API: new pull_request payloads are trimmed to the point of being inconsistent and almost useless
              
              #177735
            
            
              
                Unanswered
              
          
                  
                    
                      Fs00
                    
                  
                
                  asked this question in
                API and Webhooks
              
            Replies: 1 comment
-
| +1 I am puzzled that the pull request title was removed. It's really such a performance penalty to join the pull request data to get the title? What's the point of returning the pull request without its title, are they expecting us to make an extra HTTP request for each pull request? That can't possibly scale better than what we had before, this is a mistake. | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
Following the recent breaking changes to the Events REST API, all pull request-related events (PullRequestEvent, PullRequestReviewEvent, PullRequestReviewCommentEvent) have had the
pull_requestobject in their respective payloads trimmed of almost all fields: it now includes onlyid,url,number,headandbase. This overly aggressive trimming is very problematic because it removes fields that are used by third-party clients - one such example is the OctoDroid app - to display those events in a meaningful way without resorting to additional slower API calls. In the case of the OctoDroid app, it was mainly relying on the presence oftitleandmergedfields onpull_requestobjects (among others), which would be the very bare minimum that should be re-added to the payload.It's honestly hard to believe that all the removed pull request fields are (quoting the announcement post) "slow to generate and require costly database calls", because the
issueobject in IssueEvent/IssueCommentEvent payloads has barely been affected by the breaking changes and includes almost all the same fields as before. This makes the payloads unexplainably inconsistent between different event types and, on top of all that, the documentation page for the event types does not even detail whichissue/pull_requestfields are actually present in the payload.I also want to add that this API change has been carried out in a way that I would define as unprofessional, with very little consideration of the users of your API:
The list could go on, but others have already voiced their concerns so I won't repeat them here.
Beta Was this translation helpful? Give feedback.
All reactions