I’m executing the GET /2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id} request. The response is documented as an object of type Pull Request. This object has an attribute destination that is documented as being type Pull Request Endpoint. This has the attribute repository documented to be of type Repository. The documentation shows 18 attributes of the Repository type plus additional attributes. When I execute the request I get back 5 of the 18 attributes. My app password has full read access to all objects.
Is the API documentation simply incorrect in its definition of a Repository? Does this endpoint not actually return a Repository type object for this attribute? I’m specifically looking for the has_issues attribute to see if this correlates with a merge conflict for the PR.