Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: smarticu5 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/cc @kubernetes/sig-contributor-experience-leads |
|
@BenTheElder: GitHub didn't allow me to request PR reviews from the following users: kubernetes/sig-contributor-experience-leads. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn 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-sigs/prow repository. |
|
/cc kubernetes/sig-contributor-experience-leads |
|
@BenTheElder: GitHub didn't allow me to request PR reviews from the following users: kubernetes/sig-contributor-experience-leads. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn 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-sigs/prow repository. |
|
@smarticu5 This looks really good, and will help reduce confusion about certain CVEs that do not admit simple fixes. Please modify it so that only members of the security response committee can add the label. (The official-cve-feed label PR can show how to do so.) |
This PR adds the label
cve/wontfix. It should be used for issues which are tagged to publish to the official CVE feed, where there are no plans to issue a fix.This is not intended to conflict with ongoing issues where there is no fix planned. These issues should still use
triage/unplanned.cc @kubernetes/sig-security-leads @katcosgrove