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 own-app-lightspeed-rag-content to f4646d0 #2394

Conversation

red-hat-konflux[bot]
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Apr 2, 2025

Image created from 'https://github.com/openshift/lightspeed-rag-content?rev=01cc319475925e9c14ba462ef7ed49df4271f17c'

This PR contains the following updates:

Package Update Change
quay.io/redhat-user-workloads/crt-nshift-lightspeed-tenant/own-app-lightspeed-rag-content digest c23ec85 -> f4646d0

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

@tisnik
Copy link
Contributor

tisnik commented Apr 2, 2025

/override "ci/prow/4.17-e2e-ols-cluster"
/override "ci/prow/4.17-ols-evaluation"
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

Copy link

openshift-ci bot commented Apr 2, 2025

@tisnik: Overrode contexts on behalf of tisnik: Red Hat Konflux / ols-enterprise-contract / lightspeed-service, ci/prow/4.17-e2e-ols-cluster, ci/prow/4.17-ols-evaluation

In response to this:

/override "ci/prow/4.17-e2e-ols-cluster"
/override "ci/prow/4.17-ols-evaluation"
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

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.

@tisnik
Copy link
Contributor

tisnik commented Apr 2, 2025

/lgtm
/approve

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 2, 2025
@tisnik
Copy link
Contributor

tisnik commented Apr 2, 2025

/retest

@red-hat-konflux red-hat-konflux bot changed the title Update own-app-lightspeed-rag-content to 826d3d2 chore(deps): update own-app-lightspeed-rag-content to a105805 Apr 3, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/component-updates/component-update-own-app-lightspeed-rag-content branch from 2a5f247 to 6d8ba9c Compare April 3, 2025 17:16
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2025
@tisnik
Copy link
Contributor

tisnik commented Apr 3, 2025

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2025
Copy link

openshift-ci bot commented Apr 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tisnik

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

The pull request process is described 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

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1f735e8 and 2 for PR HEAD 6d8ba9c in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b3a2281 and 1 for PR HEAD 6d8ba9c in total

Image created from 'https://github.com/openshift/lightspeed-rag-content?rev=01cc319475925e9c14ba462ef7ed49df4271f17c'

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update own-app-lightspeed-rag-content to a105805 Update own-app-lightspeed-rag-content to f4646d0 Apr 3, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/component-updates/component-update-own-app-lightspeed-rag-content branch from 6d8ba9c to 503a2a0 Compare April 3, 2025 20:55
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2025
@tisnik
Copy link
Contributor

tisnik commented Apr 4, 2025

/override ci/prow/4.17-e2e-ols-cluster
/override ci/prow/4.17-ols-evaluation

Copy link

openshift-ci bot commented Apr 4, 2025

@tisnik: Overrode contexts on behalf of tisnik: ci/prow/4.17-e2e-ols-cluster, ci/prow/4.17-ols-evaluation

In response to this:

/override ci/prow/4.17-e2e-ols-cluster
/override ci/prow/4.17-ols-evaluation

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.

Copy link

openshift-ci bot commented Apr 4, 2025

@red-hat-konflux[bot]: all tests passed!

Full PR test history. Your PR dashboard.

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.

@tisnik
Copy link
Contributor

tisnik commented Apr 4, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 4, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 6b1887d into main Apr 4, 2025
12 of 14 checks passed
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. konflux-nudge lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants