Skip to content

[openshift-psap/topsail-ng] Introduce the configuration for the new repo#75305

Open
kpouget wants to merge 2 commits intoopenshift:mainfrom
kpouget:topsail-ng
Open

[openshift-psap/topsail-ng] Introduce the configuration for the new repo#75305
kpouget wants to merge 2 commits intoopenshift:mainfrom
kpouget:topsail-ng

Conversation

@kpouget
Copy link
Contributor

@kpouget kpouget commented Feb 25, 2026

No description provided.

@kpouget kpouget changed the title [openshift/topsail-ng] Introduce the configuration for the new repo [openshift-psap/topsail-ng] Introduce the configuration for the new repo Feb 25, 2026
@openshift-ci openshift-ci bot requested review from deepsm007 and jmencak February 25, 2026 15:40
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 25, 2026
@kpouget kpouget force-pushed the topsail-ng branch 4 times, most recently from dfabbe9 to 30b54eb Compare February 25, 2026 16:20
@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 25, 2026
@kpouget kpouget force-pushed the topsail-ng branch 2 times, most recently from fd211f4 to e50fe46 Compare February 25, 2026 16:35
@albertoperdomo2
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: albertoperdomo2, kpouget
Once this PR has been reviewed and has the lgtm label, please assign pruan-rht 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 lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 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.

  • MML-coder
    • 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.
    • ci-operator/config/openshift-psap/topsail-ng/OWNERS
    • ci-operator/jobs/openshift-psap/topsail-ng/OWNERS
    • core-services/prow/02_config/openshift-psap/topsail-ng/OWNERS

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@kpouget: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 25, 2026

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

@kpouget
Copy link
Contributor Author

kpouget commented Feb 25, 2026

/assign @deepsm007

is this fine ?

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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants