Ask HN: Why does Coveralls need to write to my repo?
I'm familiar with how Travis (and presumably other CIs) write to a repo's "status" to indicate broken builds. This morning, coveralls.io asked for perms to do the same thing, which seemed cool. After I approved that, it then asked for "read and write all public and private repo data". Github says that perm includes writing the following:
Code
Issues
Pull requests
Wikis
Settings
Webhooks and services
Deploy keys
And also Coveralls has set up a redirect loop so that if I don't submit to this indignity, I can't use that site at all. Anyone have any ideas about this?
(
7 comments
| 5 points
| on HN
)
Slack has a similar thing, but they call it out in support docs - see here: https://slack.zendesk.com/hc/en-us/articles/201824286-Settin...
Actually, I just had a dig through their FAQ and Coveralls answers this: https://coveralls.zendesk.com/hc/en-us/articles/201344219-Wh...
So basically it's a limitation on Github's side, by not providing a read-only scope for repos.
Besides, I was perfectly happy with Coveralls' service yesterday. They could make at least a token effort toward explaining what more they can do with God access.
The Github scopes are not finely grained enough for applications using them to ask for only the minimal permissions they need.
I do agree that Coveralls should explain this better, either before they ask for the permissions, or at least in their FAQs.
Whatever, it's free. I'll stop bitching.