Skip to content

Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 12:06:47 UTC#75581

Merged
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom
openshift-bot:auto-config-brancher
Mar 3, 2026
Merged

Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 12:06:47 UTC#75581
openshift-merge-bot[bot] merged 4 commits intoopenshift:mainfrom
openshift-bot:auto-config-brancher

Conversation

@openshift-bot
Copy link
Contributor

/cc @openshift/test-platform

@openshift-bot openshift-bot added tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges. rehearsals-ack Signifies that rehearsal jobs have been acknowledged 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. labels Mar 3, 2026
@openshift-ci openshift-ci bot requested a review from a team March 3, 2026 00:07
@openshift-bot openshift-bot force-pushed the auto-config-brancher branch from 6d0c51b to f200437 Compare March 3, 2026 04:07
@openshift-bot openshift-bot changed the title Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 00:07:05 UTC Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 04:07:03 UTC Mar 3, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-bot

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-bot openshift-bot changed the title Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 04:07:03 UTC Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 08:06:11 UTC Mar 3, 2026
@openshift-bot openshift-bot force-pushed the auto-config-brancher branch from f200437 to d58e7c7 Compare March 3, 2026 08:06
@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

New changes are detected. LGTM label has been removed.

…openshift-priv --only-org openshift --whitelist-file ./core-services/openshift-priv/_whitelist.yaml
…/core-services/sanitize-prow-jobs/_config.yaml
@openshift-bot openshift-bot force-pushed the auto-config-brancher branch from d58e7c7 to 176eacf Compare March 3, 2026 12:06
@openshift-bot openshift-bot changed the title Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 08:06:11 UTC Automate config brancher by auto-config-brancher job at Tue, 03 Mar 2026 12:06:47 UTC Mar 3, 2026
@openshift-bot openshift-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@openshift-bot: 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-merge-bot openshift-merge-bot bot merged commit f93d4b8 into openshift:main Mar 3, 2026
32 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

@openshift-bot: 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.

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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants