-
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/reference-docs #1158
Comments
/assign |
I've created the PR #1231 to add the additional members to k-sigs and migrate the teams. Once it merges, should be able to move the repo 👍 |
The Repo has been migrated and is now at: https://github.com/kubernetes-sigs/reference-docs OWNERS update is here: kubernetes-sigs/reference-docs#92 |
Repo was migrated from kubernetes-incubator to kubernete-sigs. For more information see the issue: kubernetes/org#1158
The repo relocation update to sigs.yaml is here: kubernetes/community#4123 Once all PRs have merged, the migration should be complete and the issue can be closed 👍 |
All PRs merged, things should be good to go! Ping me if you have any problems 👍 /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. |
Thanks, @mrbobbytables! |
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/reference-docs)
Requested name for new repository
reference-docs
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
If not a staging repo, who should have write access
If not a staging repo, who should be listed as approvers in OWNERS
If not a staging repo, who should be listed in SECURITY_CONTACTS
What should the repo description be
Tools to build reference documentation for Kubernetes APIs and CLIs.
What SIG and subproject does this fall under in sigs.yaml
This is a subproject of sig-docs
Approvals
This subproject, reference-docs, is outlined as being in-scope as part of the sig-docs charter. An issue kubernetes/website#13904 was opened after the 1.14 release about this repo moving locations as well as discussed in the 9/3 sig-docs community meeting.
Additional context for request
Since this repo is used for each release and iterated on, I would like to
/hold
the migration until 1.16 is out the door.Addt'l items:
Note: I took a guess at which users should be included as well as permissions. It could use a second set of 👀
/cc @zacharysarah @Bradamant3 @kbarnard10 @simplytunde @tengqm @kbhawkey
The text was updated successfully, but these errors were encountered: