I am using the graphql api to query RepositoryCollaboratorEdge objects to see who has access to my repo and how.   But I am noticing that some users with permissions have nothing in the permissionSources. (To be clear, I am seeing organizations, teams and repostiory objects returning in the same query for other repos/collaborators.)   For example. This query: query { viewer { repositories ( first:1 affiliations:[OWNER, ORGANIZATION_MEMBER], ownerAffiliations:[OWNER, ORGANIZATION_MEMBER] ){ totalCount pageInfo { endCursor hasNextPage } nodes { name nameWithOwner collaborators ( first:1 ) { totalCount pageInfo { endCursor hasNextPage } edges { node { login } permission permissionSources { permission source { ... on Organization { websiteUrl id name } ... on Repository { homepageUrl id name nameWithOwner } ... on Team { editTeamUrl id name combinedSlug } } } } } } } } }   Has some results for collaborators that are looking like this snippet:   "collaborators": { "totalCount": 103, "pageInfo": { "endCursor": "Y3Vyc29yOnYyOpHNA8E=", "hasNextPage": true }, "edges": [ { "permission": "WRITE", "permissionSources": [] }, { "permission": "ADMIN", "permissionSources": [] },   So my questions is: What might cause these permission sources arrays to be empty?   Maybe this is an issue with the permission levels of the caller? But it seems strange to me that I should be able to see the collaborators and there permission at all if i can't see the permissionSources.  Or perhaps there is another way to become a collaborator beyond organization membership, team membership or direct repo assignment? I'm also noticing that this appears to be happening to repos as a whole so maybe there is something there as well?   ... View more

I'm looking to retrieve all the repo permissions for a user.   Effectively something that I could massage to produce:   { "login": "myUser", "name": "myUsername", "repositories":[ { "name": "myRepo" "permissions":[ { "permission":"ADMIN", "permissionSources": ..... }, { "permission":"READ", "permissionSources": ..... } ] } ] }   The closest thing I have so far is to: lookup my user, iterate through the user's repos (unfortunately the collection here doesn't have all the nice details that RepositoryCollaboratorEdge has) iterate through those repos' collaborators get permission and permission sources   But the problem is I get ALL of the collaborators for the repo on the third step. Is there a way to filter down to just the current user somehow? Or perhaps there is another way to go about this?   Here's the query I'm describing:     query { user( login: myuser ) { name repositories(first:100, affiliations:[OWNER, ORGANIZATION_MEMBER, COLLABORATOR], ownerAffiliations:[OWNER, ORGANIZATION_MEMBER, COLLABORATOR] ) { edges { node { name nameWithOwner collaborators ( first: 100 ){ edges { permission permissionSources { source { ... on Organization { id name } ... on Repository { id name nameWithOwner } ... on Team { id name slug } } } } } } } } } }           ... View more

In the Enterprise version of github if you browse to: https://<my-github>.com/stafftools/repositories/:org/:repo/permissions you can see a table under the heading "Individual permissions" which lists out all the users who have access to this repo and the means they use to access it, showing the most permissive access.   Is there any way to get this data from the API? So far, I have only found ways to see the access level. I have not found anything that shows how the access was granted. It would be nice even if I could just grab this table programatically.     ... View more