N.B. These questions are about the GitHub end of the functionality, not the recent real world case
We recently received a request for expanded permissions for a GitHub App we have already authorized for use in the ‘mozilla’ org. We only authorize use on a per-repository basis. From the outside, it looks like these permissions might expand the amount of PII shared with the GitHub App, particularly for folks who have opted-in to less exposure.
I assume the following two permissions are “per repository”:
Read-only access to Deployments
Read-only access to Commit statuses
Q1: Am I correct about the scope of those permissions?
For the last requested permission:
Read-only access to Organization members
I have several questions:
Q2: Would this allow access to org members who are not explicitly authorized to a subscribed repository?
Q3: For members who have set ‘private’ status in the organization, would their membership be conveyed to the GitHub App?
Q4: For members who are explicitly authorized to a subscribed repository, would the GitHub App have access to their real email address, if they’ve elected to ‘keep my email address private’?
Q5: If the answer to any of Q2, Q3, or Q4 is “yes”, is the GitHub App aware of the distinction and/or required to preserve the intent of those enhance privacy settings?