Closed prb112 closed 3 months ago
Hi @prb112. Thanks for your PR.
I'm waiting for a ComplianceAsCode 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.
/jira refresh
@prb112: This pull request references Jira Issue OCPBUGS-32797, which is invalid:
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: prb112, rhmdnd
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/label qe-approved
/jira refresh
@xiaojiey: This pull request references Jira Issue OCPBUGS-32797, which is valid. The bug has been moved to the POST state.
No GitHub users were found matching the public email listed for the QA contact in Jira (xiyuan@redhat.com), skipping review request.
@prb112: Jira Issue OCPBUGS-32797: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-32797 has been moved to the MODIFIED state.
@prb112: This pull request references Jira Issue OCPBUGS-32797, which is invalid:
Comment
/jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.The bug has been updated to refer to the pull request using the external bug tracker.