-
Notifications
You must be signed in to change notification settings - Fork 687
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
REQUEST: Create kubernetes-sigs/sig-auth-tools #3688
Comments
Probably should use sig-auth-leads owner alias to cover all the leads. LGTM otherwise. |
We would need to create that alias in the new repo and use it. I think |
I feel like we should have automation for this... |
/assign |
repo created: https://github.com/kubernetes-sigs/sig-auth-tools when all PRs are merged and teams added to the repo this can be closed. |
teams have been added, the repo should now be usable 👍 |
outstanding PRs have been merged, going to go ahead and close 👍 /close |
@mrbobbytables: 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. |
Thank you @mrbobbytables! |
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
sig-auth-tools
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
enj, ritazh
Who should have write access?
enj, ritazh
Who should be listed as approvers in OWNERS?
enj, ritazh
Who should be listed in SECURITY_CONTACTS?
enj, ritazh
What should the repo description be?
Repository for tools and artifacts related to the sig-auth charter in Kubernetes.
What SIG and subproject does this fall under?
sig-auth
Please provide references to appropriate approval for this new repo
https://kubernetes.slack.com/archives/C0EN96KUY/p1663091084021459
Additional context for request
ref: kubernetes/kubernetes#111963
The text was updated successfully, but these errors were encountered: