Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update serverless-ingress-135 to 10c8c4b #3271

Conversation

red-hat-konflux[bot]
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jan 7, 2025

This PR contains the following updates:

Package Update Change
quay.io/redhat-user-workloads/ocp-serverless-tenant/serverless-operator-135/serverless-ingress digest d7ca810 -> 10c8c4b

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test

Copy link
Contributor

openshift-ci bot commented Jan 7, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign mgencur for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

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

Copy link
Contributor

openshift-ci bot commented Jan 7, 2025

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift-knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/component-updates/serverless-ingress-135 branch from 75b1ddf to f330872 Compare January 8, 2025 06:43
@red-hat-konflux red-hat-konflux bot changed the title Update serverless-ingress-135 to 49f569d Update serverless-ingress-135 to 966e5f2 Jan 8, 2025
@red-hat-konflux red-hat-konflux bot changed the title Update serverless-ingress-135 to 966e5f2 Update serverless-ingress-135 to 09230ca Jan 8, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/component-updates/serverless-ingress-135 branch from f330872 to db2cf16 Compare January 8, 2025 09:59
@red-hat-konflux red-hat-konflux bot changed the title Update serverless-ingress-135 to 09230ca Update serverless-ingress-135 to 593828b Jan 8, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/component-updates/serverless-ingress-135 branch 2 times, most recently from 1bba945 to 3e9b734 Compare January 8, 2025 15:47
@red-hat-konflux red-hat-konflux bot changed the title Update serverless-ingress-135 to 593828b Update serverless-ingress-135 to d7ca810 Jan 8, 2025
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/component-updates/serverless-ingress-135 branch from 3e9b734 to 45a8d19 Compare January 8, 2025 17:31
@red-hat-konflux red-hat-konflux bot changed the title Update serverless-ingress-135 to d7ca810 Update serverless-ingress-135 to 10c8c4b Jan 8, 2025
@pierDipi pierDipi closed this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant