-
Notifications
You must be signed in to change notification settings - Fork 713
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
github.com/kubernetes-csi/csi-lib-utils #268
Comments
/assign @saad-ali |
I approve the creation of
Let's make the description: |
/unassign @saad-ali Yeah, I can kick this out. |
Okay, should be good to go. Can you add this to sigs.yaml? |
Done: kubernetes/community#2989 Thanks a lot for the quick turn around @cblecker!! |
Cool! Please let me know if you need anything else. |
@cblecker: 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
new repository
Requested name for new repository
csi-lib-utils
Which Organization should it reside
kubernetes-csi
If not a staging repo, who should have admin access
@saad-ali
If not a staging repo, who should have write access
@saad-ali
If a new repo, who should be listed as approvers in OWNERS
@saad-ali
If a new repo, who should be listed in SECURITY_CONTACTS
@saad-ali
What should the repo description be
by default we will set it to "created due to (link to this issue)"
What SIG and subproject does this fall under in sigs.yaml
sig-storage
Approvals
Issue submitted as per @saad-ali request
Authoritative requirements are here: https://git.k8s.io/community/github-management/kubernetes-repositories.md
Additional context for request
Repo will be used for shared libraries used by CSI external components
/area github-repo
The text was updated successfully, but these errors were encountered: