updated the owners file for fix of issue 39

[menonshilpa15-rgb]

This PR is raised to update the OWNERS file for this repo - as per the issue Update OWNERS file #39

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: menonshilpa15-rgb / name: shilpa (01bf308)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: menonshilpa15-rgb
Once this PR has been reviewed and has the lgtm label, please assign iancoldwater for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @menonshilpa15-rgb!

It looks like this is your first PR to kubernetes-sigs/cve-feed-osv 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cve-feed-osv has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes-sigs org. You can then trigger verification by writing /verify-owners in a comment.

• Emeritus
  • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.

[PushkarJ]

@menonshilpa15-rgb use this example: https://github.com/kubernetes/sig-security/pull/161/files to know what changes are required

[menonshilpa15-rgb]

HI @PushkarJ

As advised , I have made the changes and below Is the updated link to the file. Kindly check and advise
#48
b1e6808

[PushkarJ]

/close

(In favor of #48)

[k8s-ci-robot]

@PushkarJ: Closed this PR.

Details

In response to this:

/close

(In favor of #48)

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.