Closed ccronca closed 3 weeks ago
Hi @ccronca. Thanks for your PR.
I'm waiting for a openshift 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.
/ok-to-test
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: raptorsun
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/override "Red Hat Konflux / ols-e2e-tests-rosa / bundle" /override "Red Hat Konflux / ols-e2e-tests-rosa / lightspeed-operator" /override "Red Hat Konflux / ols-enterprise-contract / bundle" /override "Red Hat Konflux / ols-enterprise-contract / lightspeed-operator
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-operator"
@raptorsun: Overrode contexts on behalf of raptorsun: Red Hat Konflux / ols-enterprise-contract / lightspeed-operator
@raptorsun: Overrode contexts on behalf of raptorsun: Red Hat Konflux / ols-e2e-tests-rosa / bundle, Red Hat Konflux / ols-e2e-tests-rosa / lightspeed-operator, Red Hat Konflux / ols-enterprise-contract / bundle, Red Hat Konflux / ols-enterprise-contract / lightspeed-operator
/retest-required
Remaining retests: 0 against base HEAD 0b42118da5cc43eb184ee8eb01c9cb2a7b39725f and 2 for PR HEAD ce3abde02d22f37a436ffdfa6baafcba981d2bbb in total
/retest-required
Remaining retests: 0 against base HEAD 0b42118da5cc43eb184ee8eb01c9cb2a7b39725f and 2 for PR HEAD ce3abde02d22f37a436ffdfa6baafcba981d2bbb in total
@ccronca: all tests passed!
Full PR test history. Your PR dashboard.
This update configures the SAST task to upload SARIF results to quay.io for long-term storage
Please note that this PR was automatically generated and may include unrelated changes due to automatic YAML formatting performed by
yq
The YAML files will be indented using 2 spaces, if the YAML file uses indentationless list the automation will try to keep this formatThe PR contains two separate commits:
Separating these changes into two commits simplifies the review process. The first commit focuses on indentation and formatting, while the second commit contains the semantic changes
Related: