This consists of removing the taskclusterrobot user and deleting the webhook that used to post to tc-github directly. We'll need to bother a github org admin to help us when the time comes.
I believe these two steps can be done independently: - remove the old webhooks - remove the old user To minimize log noise, it would be best to do them in the order above. Neither step is impacting on users, they are just not easily reversible. An owner is only needed for the first step (actually could be farmed out to all the repo admins, but I think centrally makes sense. Let me know when you're positive we don't have to go backwards, and I can use the etherpad to pull webhooks from the orgs I have access to. You'll need to handle taskcluster and the hooks in personal accounts.
Ok, I think we're confident we can move forward now. No rush on deleting the hooks, but whenever you get around to it, just let me know and I'll go and remove the user.
Status: NEW → ASSIGNED
Flags: needinfo?(bstack) → needinfo?(hwine)
I've removed hook from repos and orgs I had access to. Your turn ;)
Flags: needinfo?(hwine) → needinfo?(bstack)
The robot is now no longer a member of any orgs or repos and has had the old oauth tokens disabled. I think we're done here. Thanks hwine!
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.