-
Notifications
You must be signed in to change notification settings - Fork 102
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
feat: add risk label group #311
base: main
Are you sure you want to change the base?
Conversation
- add support for a risk label group as well as "needs-risk" Signed-off-by: Brian Davis <slimm609@gmail.com>
Welcome @slimm609! |
Hi @slimm609. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: slimm609 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for k8s-prow ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
is this coming from some sig meetings? could you link an associated issue? |
No, this is not coming from a meeting. Just a community contribution to support the risk category |
/hold If you want to use your own arbitrary labels for deployments of prow that are not kubernetes, the label plugin supports this already |
This is a community contribution from just consuming open source prow in github enterprise