Skip to content

NO-JIRA: Update OWNERS_ALIASES#29

Open
stephenfin wants to merge 2 commits intoopenshift:mainfrom
shiftstack:shiftstack-OWNERS
Open

NO-JIRA: Update OWNERS_ALIASES#29
stephenfin wants to merge 2 commits intoopenshift:mainfrom
shiftstack:shiftstack-OWNERS

Conversation

@stephenfin
Copy link
Copy Markdown

Follow-on to #28

/assign @mandre

pierreprinetti and others added 2 commits March 24, 2026 14:24
Remove pierreprinetti
Add dlaw4608, eschulman2. Drop former members.

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
@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

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

Details

In response to this:

Follow-on to #28

/assign @mandre

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
Copy link
Copy Markdown

openshift-ci Bot commented Mar 26, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign pierreprinetti 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:

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 do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Mar 26, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 26, 2026

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 openshift org. You can then trigger verification by writing /verify-owners in a comment.

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

Copy link
Copy Markdown
Member

@mandre mandre left a comment

Choose a reason for hiding this comment

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

Don't you want to add Ella and Daniel as approvers?

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 26, 2026

@stephenfin: The following test 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-hypershift 5c14888 link true /test e2e-hypershift

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.

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

Labels

do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants