Skip to content

KFLUXSPRT-8263: trusted git-clone-oci-ta 0.2 digest#588

Open
MitaliBhalla wants to merge 1 commit into
openshift:masterfrom
MitaliBhalla:rosa-745-trusted-git-clone-digest
Open

KFLUXSPRT-8263: trusted git-clone-oci-ta 0.2 digest#588
MitaliBhalla wants to merge 1 commit into
openshift:masterfrom
MitaliBhalla:rosa-745-trusted-git-clone-digest

Conversation

@MitaliBhalla

@MitaliBhalla MitaliBhalla commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Summary

KFLUXSPRT-8263 — align task-git-clone-oci-ta:0.2 Tekton bundle digest to the trusted entry in quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles after the platform acceptable-bundles refresh.

Trusted digest: sha256:52827a47564514f6accab971b8fad4f1c1cf59997507ed7c4e534615eeeae567

Test plan

  • Konflux *-on-pull-request green on this PR

Jira: ROSA-745 / KFLUXSPRT-8263

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 1, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 1, 2026

Copy link
Copy Markdown

@MitaliBhalla: This pull request references KFLUXSPRT-8263 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

KFLUXSPRT-8263 — align task-git-clone-oci-ta:0.2 Tekton bundle digest to the trusted entry in quay.io/konflux-ci/tekton-catalog/data-acceptable-bundles after the platform acceptable-bundles refresh.

Trusted digest: sha256:52827a47564514f6accab971b8fad4f1c1cf59997507ed7c4e534615eeeae567

Test plan

  • Konflux *-on-pull-request green on this PR

Jira: ROSA-745 / KFLUXSPRT-8263

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.

@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@MitaliBhalla, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0956e8a0-98a4-4a65-9cdc-4ac782b71a32

📥 Commits

Reviewing files that changed from the base of the PR and between 9225608 and e07ccd9.

📒 Files selected for processing (4)
  • .tekton/managed-cluster-validating-webhooks-e2e-pull-request.yaml
  • .tekton/managed-cluster-validating-webhooks-e2e-push.yaml
  • .tekton/managed-cluster-validating-webhooks-pull-request.yaml
  • .tekton/managed-cluster-validating-webhooks-push.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci openshift-ci Bot requested review from aliceh and anispate July 1, 2026 07:14
@openshift-ci

openshift-ci Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MitaliBhalla

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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 1, 2026
@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

@MitaliBhalla: 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-binary-build-success e07ccd9 link true /test e2e-binary-build-success

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.

@openshift-ci

openshift-ci Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

PR needs rebase.

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.

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 2, 2026
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants