1521235 - Please provide additional scopes for github user: kglazko and user:rpappalax

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

[Kate Glazko]

+++ This bug was initially created as a clone of Bug #1500824 +++

Please give all repos notify scopes under github user: kglazko. I am working on some Taskcluster notification with Richard P. and it would be helpful to have those scopes.

Comment 1

[Richard Pappalardo [:rpapa][:rpappalardo]]

:kglazko and I are working together. Please also add the following scopes
github:create-comment:kglazko/*
and to my repo as well
github:create-comment:rpappalax/*

Comment 2

[Brian Stack [:bstack]]

Done! I still don't think that assigning scopes to individual users accounts is the right way to go about this. Can we make a secondary repo inside the mozilla org instead or something along those lines? The way we are doing this now makes for a management nightmare.

Comment 3

[Richard Pappalardo [:rpapa][:rpappalardo]]

(In reply to Brian Stack [:bstack] from comment #2)

Done! I still don't think that assigning scopes to individual users accounts is the right way to go about this. Can we make a secondary repo inside the mozilla org instead or something along those lines? The way we are doing this now makes for a management nightmare.

Thanks so much, Brian. We certainly don't want to create a mgmt nightmare for you. The reason we asked for this is because oftentimes we need a way to verify how a change to our taskcluster config or new feature works before we merge it into any of our build/test stacks. We prefer to do that kind of experimentation in a sandbox somewhere we can control and outside of any of the project repos themselves. If we were to setup a new general-purpose project like that, I'm not sure who would be willing to own it, control the scopes, monitor proper use on that project, etc. We're certainly open to any suggestions.

Comment 4

[Brian Stack [:bstack]]

Could we make a <repo name>-testing inside the mozilla org that you do your work in? Then we wouldn't have to assign scopes outside of mozilla. You can get the mozilla org owners to make you admins of that repo afaik.