-
Notifications
You must be signed in to change notification settings - Fork 167
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
Provide temporary access to @gireeshpunathil to AIX CI machines #463
Comments
Sounds good to me. Will you handle his pubkey and show him the ropes? (copy repo, take bot out of action, etc) |
@mhdawson sounds good to me as well! |
I'll add his public key to one of the AIX machines and co-ordinate with respect to other interaction required. Since the AIX builds only run once a night the co-ordination with existing builds should be limited. |
@mhdawson - the purpose of this temporary access is achieved, and the access can now be revoked. Thanks to the approvers and endorsers. |
@mhdawson Can you confirm access has been revoked? |
Deleted the user I had setup for @gireeshpunathil |
Gireesh works at IBM with me and need access to the new AIX machines in order to investigate:
nodejs/node#7973
I think he meets the requirements for temporary access in: https://github.com/nodejs/build/blob/master/doc/process/special_access_to_build_resources.md based on this subset of the criteria:
as far back as March 2015.
definitely have an impact
@nodejs/build can I get an approver ?
The text was updated successfully, but these errors were encountered: