Hello,
Responding to your comment in #sig-testing slack. I have been working
on some improvements for the testing infra recently that center around
making the `do-not-merge` label a class of labels, in order to allow
bots and users to add and remove specific reasons for blocking merges
while keeping some reasons locked down.
I posted to kubernetes-sig-testing [1] to ask for the following labels
to be made so we can enable the new features:
kubernetes/* [ on repos where the submit-queue is enabled, but could
be useful in general ]
- do-not-merge/hold
- do-not-merge/work-in-progress
kubernetes/kubernetes
- do-not-merge/release-note-label-needed
- do-not-merge/cherry-pick-not-approved
- do-not-merge/blocked-paths
Please let me know if there is anything I need to do to help you add
these labels, or otherwise.
Thanks for your time,
Steve
[1] https://groups.google.com/forum/#!topic/kubernetes-sig-testing/Q4R2aPuK4h0
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-wg-contribex/CAPgXYS7JEHNem9r5h0U6OWojpjL52D5%2BWZGQ01h3iE4pHnHpkg%40mail.gmail.com.--
You received this message because you are subscribed to the Google Groups "kubernetes-wg-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-wg-contribex+unsub...@googlegroups.com.
To post to this group, send email to kubernetes-wg-contribex@googlegroups.com.