-
Notifications
You must be signed in to change notification settings - Fork 395
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
Add all maintainers to k8s.io OWNERS #1156
Comments
/unassign @EleanorRigby |
@kkeshavamurthy I see that if you try to join the kubernetes org, it says:
So you should be able to make a pull request directly against kubernetes/org as described here by adding yourself to |
/close |
@mboersma: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I closed this prematurely: see kubernetes/k8s.io#5369 |
/close This time for reals. |
@mboersma: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
In trying to sync up housekeeping files with current image-builder owners (see kubernetes/k8s.io#5263), I wasn't able to add @EleanorRigby or @kkeshavamurthy because they're not yet members of the kubernetes GitHub org.
Membership in kubernetes-sigs is transferable to kubernetes, so this should be just a matter of requesting membership. When that is granted, we can create PRs to grant appropriate owner access.
/kind feature
/assign @kkeshavamurthy @EleanorRigby
The text was updated successfully, but these errors were encountered: