-
Notifications
You must be signed in to change notification settings - Fork 667
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
new repo: kubernetes-sigs/structured-merge-diff #70
Comments
/assign |
Created
@lavalamp @apelisse are team maintainers for both teams @jennybuckley has been invited to structure-merge-diff-maintainers and to the kubernetes-sigs org since they're already a kubernetes member |
/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. |
Thanks for the rapid response!!
…On Thu, Sep 6, 2018 at 2:10 PM k8s-ci-robot ***@***.***> wrote:
Closed #70 <#70>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#70 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAngli6dI4rbMTIvbUp9YS3NiuYVBCcPks5uYY9fgaJpZM4WdaCO>
.
|
New Repo, or migrate existing
new repository
Requested name for new repository
structured-merge-diff
Which Organization should it reside
kubernetes-sigs
Who should be provided access to this repository
@lavalamp, @apelisse, @jennybuckley (write)
Approvals
SIG leads are agreed, see discussion in kubernetes/community#2577
The text was updated successfully, but these errors were encountered: