-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Add cve-feed-osv project #7966
Add cve-feed-osv project #7966
Conversation
Signed-off-by: Madhav Jivrajani <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MadhavJivrajani The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @kubernetes/sig-security-leads |
@@ -2815,6 +2815,7 @@ sigs: | |||
contact: | |||
slack: sig-security-tooling | |||
owners: | |||
- https://raw.githubusercontent.com/kubernetes-sigs/cve-feed-osv/main/OWNERS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PushkarJ can you confirm if adding it as a project under the sig-security-tooling
subproject is accurate or do we require a new subproject to be created?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this mostly for documentation purposes or does this mean some permissions like approving or lgtm will be granted to owners of that subproject?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's documentation purposes it's fine to keep the sub-project as sig-security-tooling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just documenting @PushkarJ :)
Will need an lgtm from a sig security lead though!
/lgtm |
/hold cancel |
Ref kubernetes/org#4873
/hold