On 15/06/17 20:05, Stephen Finucane wrote:
You're going to have the exact same situation if we add "CI" users. Someone,
somewhere, has to approve these requests if we don't want to simply allow any
user to create checks.
Well, you could allow *maintainers* to authorise CI users somewhere in
On Thu, 2017-06-15 at 14:37 +1000, Andrew Donnellan wrote:
> On 07/06/17 02:28, Stephen Finucane wrote:
> > On Tue, 2017-06-06 at 21:10 +1000, Daniel Axtens wrote:
> > > What actually is required? We probably want to make this reasonably
> > > granular so that, for example, the 0-day bot can be
On 07/06/17 02:28, Stephen Finucane wrote:
On Tue, 2017-06-06 at 21:10 +1000, Daniel Axtens wrote:
Hi,
One thing that has come up in discussions around CI and Patchwork is
permissions for the checks API.
What permissions are required for a user to create a check?
I can't find anything in the
Hi,
One thing that has come up in discussions around CI and Patchwork is
permissions for the checks API.
What permissions are required for a user to create a check?
I can't find anything in the docs to tell me for sure.
I know that admin permissions are sufficient, and I have been unreliably
