I would have agreed with this, but the permissions they ask for are pretty benign and clearly relevant to their mission.

I'm a member of organisations that may not be comfortable with me giving permission by proxy.

I couldn't find a way to sign up and exclude private repos or organizations.

Fair enough, but I think that's a limitation of Github rather than a problem imposed by Percy.

Percy.io's Invite Request system is tied to github.

How is that not a problem imposed by Percy?

I'd feel more comfortable having a different mechanism to request an invite.

While the permissions don't grant Code Access, it does ask to read Organization and Team membership. I'd expose data for every member of my companies github organization to Percy, JUST for an invite.

Percy is a tool that integrates with Github to set build status on Github pull requests. Of course it needs to tie into Github.

100 %.

However:

Sign up for Service != Sign up for Invite.

Indeed, but it seems reasonable to me that they wouldn't need to make two systems for storing user information.

You can sign up for the mailing list instead: https://percy.io/#updates

And yes it's a GitHub limitation, we request some limited readonly access and no code access (we don't need it).

That's weird, because I'm a member of an org that Github explicitly requires you approve this access for apps like this.

is this tool any good? anyone used percy and can give a brief review of how they thought it was / what worked well? thank you.