Through the existing API, you can fetch pull request author, repo owner of the source of the pull request, assignees, users that merges the pull request, and get commits with committers and authors. What are you looking for specifically?

I want to find the code owners requested for review on a specific PR. It doesn’t seem possible through the API.

https://help.github.com/en/articles/about-code-owners

> Code owners are automatically requested for review when someone opens a pull request that modifies code that they own.

So you could query requested reviewers.

I wanted to identify if a requested reviewer was requested as a code owner.

Hi @chdsbd!

While it’s not possible to do this with a single API, you can create a script that allows you to crossreference the requested reviewers with the content of the CODEOWNERS file using the Get Contents API endpoint. Since the CODEOWNERS file has a limited number of locations that it can be located, it should be easy to find with a couple of calls.

Hope that helps!

Thanks. That’s what I’ve settled on. The challenge I see is that a user could be in the code owners file but not necessarily be requested because of their ownership. Another user could request their review for code they don’t own.

@chdsbd, that’s very true. You’d probably have to do some advanced checking of the files in the PR and how they compare to the CODEOWNERS file as well to be sure. 

@that-pat, we have similiar request to check whether the approval is coming from code owner or not, does GitHub have any plan to expose one single API for code owner check?

It seems like reviewDecision should work for my use case, but there’s a bug with the field that’s preventing me from using it.

The reviewDecision field causes the GitHub GraphQL API to error when “Require review from Code Owners” is enabled and the pull request has a file matching CODEOWNERS. I have a ticket open with GitHub Support about this.

Hey @chdsbd thanks so much for voicing your experience. Very curious to know how your exchange goes with that internal support ticket.

If anything seems relevant for the Community, would you mind posting back?

Anyone else reading is also empowered to @ mention me and I can see if there was traction that might be suited for a broader audience, than the 1:1 ticket mentioned above.

🙇

@nethgato I’m pinging you because we’d really need to have code owner reviews exposed for the REST API too. Is there anything we can help with?

Hi @jd o/

As-is, the best thing you could do, is to add your voice to those who would like to see similar data in REST, as we have in GraphQL. The most helpful path forward, would be to submit via our feedback form, here:

Share feedback - GitHub Support

//support.github.com/contact/feedback

This is the best way I’ve found to do this:

1. List requested reviewers for a pull request using the following API: https://docs.github.com/en/github-ae@latest/rest/reference/pulls#list-requested-reviewers-for-a-pull-request. This will give you a list of usernames and a list of teams.
2. Codeowners are essentially just teams or individuals assigned to watch over certain parts of the codebase. In my case, I wanted a list of usernames who are part of each codeowning team. For this I used the Teams API: https://docs.github.com/en/rest/reference/teams#list-team-members.

Caveats of this approach:

• Step 1 of this approach lists out all of those whose reviews were requested on the PR. While Github automatically requests reviews from codeowning individuals and teams, one can manually request reviews as well. This step does not distinguish between automatic review requests (which suggest codeowner status) and manual review requests.

I see the information is available, but not in the API .... e.g.

curl https://github.com/dotnet/samples/deferred-metadata/main/machine-learning/models/sentimentanalysis/sentiment_model.zip

gives

{
  "showCodeNavSurvey": false,
  "showLicenseMeta": false,
  "license": null,
  "newIssuePath": "/dotnet/samples/issues/new",
  "newDiscussionPath": null,
  "codeownerInfo": {
    "codeownerPath": "/dotnet/samples/blob/main/.github/CODEOWNERS#L21",
    "ownedByCurrentUser": false,
    "ownersForFile": "@luisquintanilla",
    "ruleForPathLine": 21
  }
}

When used on a private repo authentication has to be done using a user_session cookie, an API token does not work.
Simply allowing auth using an API token here would be a step forward, although I can understand that a more principled addition to the API would be better.