Closed dystewart closed 3 years ago
Hi @dystewart. Thanks for your PR.
I'm waiting for a operate-first 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.
Hey @dystewart thanks! Can you squash your commits down to one? See the third point here for more details on the reasoning behind squashing.
@HumairAK removed the previous commit
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: HumairAK
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@dystewart: The following tests failed, say /retest
to rerun all failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
aicoe-ci/prow/pre-commit | 4404a5df2f1a1ebf09eb1276b2c6440ea25de943 | link | /test pre-commit |
community-management/prow/peribolos | 4404a5df2f1a1ebf09eb1276b2c6440ea25de943 | link | /test peribolos |
Full PR test history. Your PR dashboard. Please help us and open an issue when you hit one in your PR.
This request is to add me to the github org.