SrBrahma
commented
4 years ago There is an easier way to achieve that. I actually found a workaround in GitHub forum and implemented it in branch wip2 (unfortunately it has so many and different changes that it became like a dead lock of confusion), that to get the orgs repos at the time that I tested, it's needed to only add this affiliations in the already existing GraphQL query. (and also, in the OAuth/token, add the 'user' if I am not mistaken).
However, the repositories tree view became a little mess with the orgs repos. I thought of implementing another tree child on the root, for the user and the repos, where the corresponding repos would be.
New query that allows orgs repos: src/octokit/commands/getRepos.ts in branch wip2
query getRepos ($after: String) {
viewer {
repositories(
first: 100,
affiliations: [OWNER, ORGANIZATION_MEMBER, COLLABORATOR], ownerAffiliations:[OWNER, ORGANIZATION_MEMBER, COLLABORATOR],
orderBy: {field: NAME, direction: ASC}, after: $after
) {
pageInfo {
endCursor
hasNextPage
}
nodes {
name
description
owner {
login
}
primaryLanguage {
name
}
url
isPrivate
isFork
isTemplate
parent {
name
owner {
login
}
}
createdAt
updatedAt
}
}
}
}
`;
jonathan-fielding
This is an initial attempt at getting organisations support working with only readOrgs permission. So far I only got this working with personal access token though but wanted to share my progress so far to see if you have any pointers for OAuth method.
Todo:
OAuth workingDONE