no-jira: Adds mytreya-rh to the OWNERS #33
Conversation
|
/retitle Adds mytreya-rh to the OWNERS |
|
/lgtm |
3aa76eb to
58c1c19
Compare
|
/lgtm |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
@mytreya-rh: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
@mytreya-rh: This pull request explicitly references no jira issue. In 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mytreya-rh, TrilokGeer 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 |
As i will be leading the external-secrets-operator work and reviewing the PRs, i would need to be able approve the PRs raised in this repo.
i read and fully understand the roles and responsibilities.
Seeking exception for the below 2 requirements:
i have perhaps reviewed 4 substantial PRs during the ESO 1.0 work, and in total about 10 PRs overall.