Skip to content

no-jira: Update OWNERS_ALIASES to include myself + "taanyas" and "marty-power"#2908

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
mattedallo:add-core-reviewers
Mar 26, 2026
Merged

no-jira: Update OWNERS_ALIASES to include myself + "taanyas" and "marty-power"#2908
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
mattedallo:add-core-reviewers

Conversation

@mattedallo
Copy link
Copy Markdown
Contributor

@mattedallo mattedallo commented Feb 16, 2026

Update OWNERS_ALIASES to include myself ("mattedallo") + "taanyas" and "marty-power" as reviewers.
Remove "ricky-rav" as he left Red Hat.
Removed some trailing spaces.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e891534c-905f-460f-9dbb-a46fdc32fb76

📥 Commits

Reviewing files that changed from the base of the PR and between 248f366 and d8c7bbf.

📒 Files selected for processing (1)
  • OWNERS_ALIASES
🚧 Files skipped from review as they are similar to previous changes (1)
  • OWNERS_ALIASES

Walkthrough

Updated OWNERS_ALIASES core-reviewers list: removed trailing whitespace from several entries and added three new aliases (marty-power, mattedallo, taanyas). No other sections or code were changed.

Changes

Cohort / File(s) Summary
Alias Configuration
OWNERS_ALIASES
Whitespace corrections to existing core-reviewers entries and addition of three new aliases: marty-power, mattedallo, taanyas.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

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

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

@openshift-ci openshift-ci bot requested review from pliurh and tssurya February 16, 2026 08:18
@openshift-ci openshift-ci bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 16, 2026
core-reviewers:
- arghosh93
- arkadeepsen
- arkadeepsen
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

was there a trailing whitespace? here and for peri? seems unrelated change hence asking

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes, I removed them (actually AI did once I asked to order alphabetically :D )

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Feb 16, 2026

/lgtm

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 16, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 16, 2026
@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Feb 16, 2026

/hold

I'd wait till Tanya becomes an org member, else its technically incorrect to add her github user handle from security perspective
feel free to remove the hold after the org member addition happens and bot is happy here #2908 (comment)

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 16, 2026
@taanyas
Copy link
Copy Markdown

taanyas commented Feb 16, 2026

/verify-owners

@openshift-ci openshift-ci bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 16, 2026
@taanyas
Copy link
Copy Markdown

taanyas commented Feb 16, 2026

/remove-hold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 16, 2026
@mattedallo
Copy link
Copy Markdown
Contributor Author

/retest-required

2 similar comments
@mattedallo
Copy link
Copy Markdown
Contributor Author

/retest-required

@mattedallo
Copy link
Copy Markdown
Contributor Author

/retest-required

… as reviewers, clean up formatting, and remove "ricky-rav" as he left Red Hat.

Signed-off-by: Matteo Dallaglio <mdallagl@redhat.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2026
@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Mar 26, 2026

/lgtm

@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Mar 26, 2026

/retest-required

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

openshift-ci bot commented Mar 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattedallo, pliurh, tssurya

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

@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Mar 26, 2026

/verified by CI

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

@pliurh: 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.

@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Mar 26, 2026

/retitle no-jira: Update OWNERS_ALIASES to include myself + "taanyas" and "marty-power"

@openshift-ci openshift-ci bot changed the title Update OWNERS_ALIASES to include myself + "taanyas" and "marty-power" no-jira: Update OWNERS_ALIASES to include myself + "taanyas" and "marty-power" Mar 26, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 26, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

Details

In response to this:

Update OWNERS_ALIASES to include myself ("mattedallo") + "taanyas" and "marty-power" as reviewers.
Remove "ricky-rav" as he left Red Hat.
Removed some trailing spaces.

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.

@pliurh
Copy link
Copy Markdown
Contributor

pliurh commented Mar 26, 2026

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit f5e61cd into openshift:master Mar 26, 2026
12 of 15 checks passed
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 26, 2026

@mattedallo: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-serial-1of2 248f366 link true /test e2e-aws-ovn-serial-1of2
ci/prow/security d8c7bbf link false /test security

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.

@mattedallo
Copy link
Copy Markdown
Contributor Author

Thanks @pliurh

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. 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.

5 participants