-
Notifications
You must be signed in to change notification settings - Fork 702
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
Migrate kubernetes-incubator/cluster-proportional*-autoscaler to kubernetes-sigs #1823
Comments
/assign @thockin |
Thanks! /lgtm |
/assign |
Creating teams prior to move: #1824 |
Transferred https://github.com/kubernetes-sigs/cluster-proportional-autoscaler |
Transferred https://github.com/kubernetes-sigs/cluster-proportional-vertical-autoscaler |
/close |
@spiffxp: 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. |
New Repo, Staging Repo, or migrate existing
Migrate existing
From
To
If not a staging repo, who should have admin access
@bowei
@dnardo
@MrHohn
@thockin
If not a staging repo, who should have write access
same as above
If not a staging repo, who should be listed as approvers in OWNERS
use existing
If not a staging repo, who should be listed in SECURITY_CONTACTS
use existing
What should the repo description be
use existing
What SIG and subproject does this fall under in sigs.yaml
sig-network/cluster-proportional*-autoscaler
Approvals
/cc @thockin
Additional context for request
This is part of kubernetes/community#1922 (comment)
The text was updated successfully, but these errors were encountered: