Granular permissions about scrutinizer HOT 7 OPEN

We are using the permissions for setting up the repository hook, this is also why the user that adds the repository has to have admin rights.

from scrutinizer.

But this hook could be set up manually right? In which case read access would be enough. I understand that it would make the set up process slightly more cumbersome, but for some organisations/people giving admin rights is understandably not acceptable.

from scrutinizer.

Yeah definitely, we have been thinking about some alternative set-up, unfortunately at the moment, we do not have it.

from scrutinizer.

Just to illustrate (because yeah it's still me rambling about this:P), those are the permissions travis asks for, and I happily give them that:

Scrutinizer on the other hand asks me for writing-code access as far as I understand:

What I mean is.. travis has the hook set up permission and then the perms to write status on PRs and stuff it seems (I guess that's Access commit status / Access deployment status?). I don't see what scrutinizer needs that is not encompassed in there.

from scrutinizer.

@Seldaek, wow, you found this one fast :) I'll put someone on this to review if we can change it easily. I just don't want to break stuff for existing customers.

@theofidry, I assume you were referring to private repositories? For those, GitHub provides no way to request read-only access unfortunately (we would be happy with that), it's also not possible to request access to just a few repositories. If we are missing something here, please let me know.

from scrutinizer.

I cheated, he linked me to it ;)

from scrutinizer.

@schmittjoh actually I wasn't making any distinction between private or public ones. If there is differences in permissions managements sorry I didn't checked that far :p

But I think @Seldaek illustrate well the issue. Thanks for taking a look.

from scrutinizer.