-
Notifications
You must be signed in to change notification settings - Fork 711
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 cluster-capacity to kubernetes-sigs #1529
Comments
/sig scheduling Sounds good to me. |
/assign |
The repo has been migrated: http://github.com/kubernetes-sigs/cluster-capacity Once the update is merged, the migration should be complete 👍 |
That was quick, the sig project list has been updated and the repo migration should be complete. /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. |
New Repo, Staging Repo, or migrate existing
migrate existing (https://github.com/kubernetes-incubator/cluster-capacity)
Requested name for new repository
cluster-capacity
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
@ingvagabund
If not a staging repo, who should have write access
@ingvagabund
If not a staging repo, who should be listed as approvers in OWNERS
@ingvagabund
If not a staging repo, who should be listed in SECURITY_CONTACTS
@ingvagabund
What should the repo description be
Cluster capacity analysis
What SIG and subproject does this fall under in sigs.yaml
sig-scheduling
Approvals
kubernetes/kubernetes#85399 (comment)
Additional context for request
None
The text was updated successfully, but these errors were encountered: