3 ms·
Judging by the screenshots of the product, it seems like repo:status is the permission that you should be asking for instead of repo. It's still read/write, but
by curun1r 12y ago
Judging by the screenshots of the product, it seems like repo:status is the permission that you should be asking for instead of repo. It's still read/write, but only to commit statuses and not code.
Is there something that your product is doing that requires read access to the code?
- bbrunner 12y agoI tried repo:status but from my testing I wasn't able to list private repos. So even though I might be able to get their commits I had no way of discovering all of the private repos for a person/org. I'll reinvestigate this as soon as I'm off the caltrain and have decent internet :)
- res0nat0r 12y agoI think r/w access is due to a limitation in the permissions from Github. Hopefully they will make this more fine-grained soon. https://slack.zendesk.com/hc/en-us/articles/201824286-Why-does-Slack-need-read-write-access-to-all-of-my-GitHub-repos- https://slack.zendesk.com/hc/en-us/articles/201824286-Why-do...