Skip to content

update owners - #295

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
shiftstack:update_owners
Aug 19, 2026
Merged

update owners#295
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
shiftstack:update_owners

Conversation

@dlaw4608

@dlaw4608 dlaw4608 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@openshift-ci
openshift-ci Bot requested review from eshulman2 and rlobillo July 16, 2026 16:17
@danchild

danchild commented Jul 20, 2026

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 20, 2026
@winiciusallan winiciusallan mentioned this pull request Jul 21, 2026
Closed
winiciusallan
winiciusallan reviewed Jul 22, 2026
View reviewed changes
Comment thread OWNERS_ALIASES Outdated
Comment on lines 21 to 27

@winiciusallan winiciusallan Jul 22, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think it'd be good to update these lists as well. From what I can tell, they are not on the team anymore, right?

@dlaw4608 dlaw4608 Jul 22, 2026

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.

Done!

@dlaw4608
update owners
69daab3 
Signed-off-by: Daniel Lawton <dlawton@redhat.com>
@openshift-ci openshift-ci Bot added do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. and removed lgtm Indicates that a PR is ready to be merged. labels Jul 22, 2026
@winiciusallan

winiciusallan commented Jul 22, 2026

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2026
@eurijon

eurijon commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

hey @dlaw4608 @winiciusallan any update on this?

mandre
mandre reviewed Aug 17, 2026
View reviewed changes

@mandre mandre left a comment

Copy link
Copy Markdown
Member

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 commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

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 Aug 17, 2026
@tusharjadhav3302

tusharjadhav3302 commented Aug 19, 2026

Copy link
Copy Markdown

/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 Aug 19, 2026
@tusharjadhav3302

tusharjadhav3302 commented Aug 19, 2026

Copy link
Copy Markdown

/verified

@openshift-ci-robot

openshift-ci-robot commented Aug 19, 2026

Copy link
Copy Markdown

@tusharjadhav3302: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified

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.

@tusharjadhav3302

tusharjadhav3302 commented Aug 19, 2026

Copy link
Copy Markdown

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 19, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 19, 2026

Copy link
Copy Markdown

@tusharjadhav3302: The verified label has been added.

Details

In response to this:

/verified bypass

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 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit aac882b into openshift:main Aug 19, 2026
5 checks passed
@openshift-merge-bot
openshift-merge-bot Bot deleted the update_owners branch August 19, 2026 10:51
@dlaw4608

dlaw4608 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.22

@dlaw4608

dlaw4608 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.21

@dlaw4608

dlaw4608 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 19, 2026
Open
@openshift-cherrypick-robot

openshift-cherrypick-robot commented Aug 19, 2026

Copy link
Copy Markdown

@dlaw4608: new pull request created: #315

Details

In response to this:

/cherry-pick release-4.22

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.

@openshift-cherrypick-robot

openshift-cherrypick-robot commented Aug 19, 2026

Copy link
Copy Markdown

@dlaw4608: new pull request created: #316

Details

In response to this:

/cherry-pick release-4.21

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 19, 2026
Open
@openshift-cherrypick-robot

openshift-cherrypick-robot commented Aug 19, 2026

Copy link
Copy Markdown

@dlaw4608: new pull request created: #317

Details

In response to this:

/cherry-pick release-4.20

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 19, 2026
Open
@dlaw4608

dlaw4608 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.19

@dlaw4608

dlaw4608 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.18

@openshift-cherrypick-robot

openshift-cherrypick-robot commented Aug 19, 2026

Copy link
Copy Markdown

@dlaw4608: #295 failed to apply on top of branch "release-4.19":

Applying: update owners
Using index info to reconstruct a base tree...
M	OWNERS_ALIASES
Falling back to patching base and 3-way merge...
Auto-merging OWNERS_ALIASES
CONFLICT (content): Merge conflict in OWNERS_ALIASES
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 update owners
Details

In response to this:

/cherry-pick release-4.19

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.

@openshift-cherrypick-robot

openshift-cherrypick-robot commented Aug 19, 2026

Copy link
Copy Markdown

@dlaw4608: #295 failed to apply on top of branch "release-4.18":

Applying: update owners
Using index info to reconstruct a base tree...
M	OWNERS_ALIASES
Falling back to patching base and 3-way merge...
Auto-merging OWNERS_ALIASES
CONFLICT (content): Merge conflict in OWNERS_ALIASES
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 update owners
Details

In response to this:

/cherry-pick release-4.18

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.

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

Reviewers

@mandre mandre mandre left review comments
@eshulman2 eshulman2 Awaiting requested review from eshulman2
@rlobillo rlobillo Awaiting requested review from rlobillo
+1 more reviewer
@winiciusallan winiciusallan winiciusallan left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

@mandre mandre

@danchild danchild

@winiciusallan winiciusallan

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@dlaw4608 @danchild @winiciusallan @eurijon @tusharjadhav3302 @openshift-ci-robot @openshift-cherrypick-robot @mandre