org
org copied to clipboard
kubernetes
REQUEST: Create kubernetes-sigs/sig-auth-tools
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: https://github.com/kubernetes/kubernetes/issues/111963
Probably should use sig-auth-leads owner alias to cover all the leads.
LGTM otherwise.
Probably should use sig-auth-leads owner alias to cover all the leads.
We would need to create that alias in the new repo and use it. I think sig-auth-leads is now only relevant in k/k?
Probably should use sig-auth-leads owner alias to cover all the leads.
We would need to create that alias in the new repo and use it. I think
sig-auth-leadsis now only relevant in k/k?
I feel like we should have automation for this...
repo created: https://github.com/kubernetes-sigs/sig-auth-tools teams added in : #3768 subproject added: https://github.com/kubernetes/community/pull/6924
when all PRs are merged and teams added to the repo this can be closed.
outstanding PRs have been merged, going to go ahead and close 👍
/close
@mrbobbytables: Closing this issue.
In response to this:
outstanding PRs have been merged, going to go ahead and close 👍
/close
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.
