Skip to content

NO-JIRA: [release-4.19] Add new team members to OWNERS#699

Open
davidesalerno wants to merge 1 commit intoopenshift:release-4.19from
davidesalerno:add-me-to-owners-419
Open

NO-JIRA: [release-4.19] Add new team members to OWNERS#699
davidesalerno wants to merge 1 commit intoopenshift:release-4.19from
davidesalerno:add-me-to-owners-419

Conversation

@davidesalerno
Copy link
Copy Markdown
Contributor

@davidesalerno davidesalerno commented Dec 4, 2025

This PR is a manual checcry-pick of #670

As a new member of the NID team I'm adding my github username to the OWNERS file

The backport is adding also @rikatz to the OWNERS file as well

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 4, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@davidesalerno: This pull request explicitly references no jira issue.

Details

In response to this:

This PR is a manual checcry-pick of #670

As a new member of the NID team I'm adding my github username to the OWNERS file

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.

@openshift-ci openshift-ci bot requested review from candita and ironcladlou December 4, 2025 14:32
@davidesalerno davidesalerno force-pushed the add-me-to-owners-419 branch 2 times, most recently from f8963fd to 1fb62dd Compare December 4, 2025 18:39
Signed-off-by: Davide Salerno <dsalerno@redhat.com>
@davidesalerno davidesalerno changed the title [release-4.19] NO-JIRA: Add davidesalerno to OWNERS [release-4.19] NO-JIRA: Add new team members to OWNERS Dec 4, 2025
Copy link
Copy Markdown
Contributor

@alebedev87 alebedev87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Dec 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 4, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Dec 4, 2025

@davidesalerno: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@alebedev87
Copy link
Copy Markdown
Contributor

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@alebedev87: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@candita
Copy link
Copy Markdown
Contributor

candita commented Mar 25, 2026

/retitle NO-JIRA: [release-4.19] Add new team members to OWNERS
Proactively adding oneself to OWNERS in an older release is not a risk.
/label backport-risk-assessed

@openshift-ci openshift-ci bot changed the title [release-4.19] NO-JIRA: Add new team members to OWNERS NO-JIRA: [release-4.19] Add new team members to OWNERS Mar 25, 2026
@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 25, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 25, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 013e1047-1e60-4e13-92b7-1bd63f4b3821

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants