We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Along with @miladfarca, @sam-github is going to be helping more with the IBM platforms.
I'd like him to help setup the new machines outlined in: #1705 so I'd like the ok to give him access to those machines as well.
Based on our criteria in: https://github.com/nodejs/build/blob/master/doc/process/special_access_to_build_resources.md
I believe he qualifies for ongoing access as:
My request is that I be able to add he's keys to all of machines supporting the IBM platforms.
The text was updated successfully, but these errors were encountered:
+1 Also +1 for permanent access.
Sorry, something went wrong.
Going to move forward with adding Sam's keys.
I have keys for rhel72-s390x-3 and rhel72-s390x-1, but not -2.
I'm on the build-wg, have access to build and release.
No branches or pull requests
Along with @miladfarca, @sam-github is going to be helping more with the IBM platforms.
I'd like him to help setup the new machines outlined in: #1705 so I'd like the ok to give him access to those machines as well.
Based on our criteria in: https://github.com/nodejs/build/blob/master/doc/process/special_access_to_build_resources.md
I believe he qualifies for ongoing access as:
consequences for mis-behaviour.
My request is that I be able to add he's keys to all of machines supporting the IBM platforms.
The text was updated successfully, but these errors were encountered: