Github also makes their OAuth permissions picker extremely confusing. When I "login with Github" I am never sure exactly what I'm sharing, from which organizations I'm a member of.
Github also makes their OAuth permissions picker extremely confusing. When I "login with Github" I am never sure exactly what I'm sharing, from which organizations I'm a member of.
Do they? You don't have to mess with syncing teams, memberships, or assignment to repos if you don't want to. You can make one api call:
> The authenticated user has explicit permission to access repositories they own, repositories where they are a collaborator, and repositories that they can access through an organization membership.
https://docs.github.com/en/rest/repos/repos?apiVersion=2022-...
So I'd give it about a 50:50 chance of working.
Edit: I just realized it eats your non-gated notifications too, if they're further down than position 25, and the "Next" button just leads to the same page with "?query=". Yay, another ticket about how glued on GitHub Enterprise Cloud is. The last one (GitHub eats API calls to accept invites to SAML organizations, deletes the invite, and sends a 200, writes success to the audit log... but ends up being a no-op) only has been 2 months or so ago. Thanks Microsoft.
"Our engineering team has indicated they will not be able to fully dive in and implement any resolutions in the near-term."
Considering they didn't in the past 7 years, I have little hope for the next 7.
I ended up using the GraphQL API and making a query like this:
query($cursor0: String, $cursor1: String) {
search(query:"org:peterldowns", type: REPOSITORY, first: 100, after: $cursor0) {
pageInfo {
hasNextPage
endCursor
}
repositories: nodes {
... on Repository {
id
name
collaborators(first: 100, after: $cursor1) {
pageInfo {
hasNextPage
endCursor
}
edges {
permission
node {
login
id
}
}
}
}
}
}
}
Removing permissions that are no longer present in this result set is left as an exercise for the reader.I stopped working on the product so I never implemented the event stream consumer that would let me listen for "this user was removed as a collaborator" or "this team no longer has admin access to that repo". The entire permissioning model for Github is extremely complex and learning about all of its intricacies was half the battle.
I did a full writeup here: https://notes.acuteaura.net/posts/github-enterprise-security...