Easy trigger path for non allowed collaborators

[lissyx]

Consider a repo Github with TaskCluster and the default configuration of allowPullRequests. When someone (new contributor) does a PR against us, TaskCluster will refuses to perform anything.

Current workflow implies that one collaborator would have to trigger the test by himself, by doing a new PR. While it works, it may become quickly non scalable. It would be great if one known collaborator could have a quickier way to perform those steps, directly after performing a review of the code.

This way the workflow would be simpler:

• new contributor pushes code, opens PR and asks for review
• reviewer takes a look, if he judges this is good enough, triggers a build

I have no overview how much that is doable.

[djmitche]

Thanks! I moved this to https://github.com/taskcluster/taskcluster-github/issues/214 - I think it's a good idea, something we've talked about informally, and is small enough (relative to TC as a whole) that it doesn't need to go through the RFC process.