-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access for Richard Lau #335
Comments
I've had previous private discussions with @mhdawson (I think around the time we were renaming the branches from |
Sounds good to me 👍🏻 The list of people having access to those secrets would benefit from being revisited, that goes for the @nodejs/github-bot team too. |
I've gone ahead and removed maclover7 and williamkapke as they have both been absent from the core project for years, as far as I know. If there are others to be removed, let me know here or (if you prefer) privately. (My email is in my GitHub profile.) If Richard wants to add himself to the team, he is an org owner and can do it himself, so I'll leave that alone either way. |
From build WG meeting: @rvagg has access and will add the access for Richard |
Now sorted 🎉. |
Richard Lau (@richardlau) does not apparently have access to the relevant secrets for the GitHub bot. Let's add him, please?
@nodejs/github-bot @nodejs/build
The text was updated successfully, but these errors were encountered: