Closed mini-bot closed 1 year ago
[REVIEW NOTIFICATION]
This pull request has not been approved.
To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer
in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer
in the comment to help you merge this pull request.
The full list of commands accepted by this bot can be found here.
/cherry-pick-invite
@zuo-bot-1 Please accept the invitation then you can push to the cherry-pick pull requests. Comment with "/cherry-pick-invite" if the invitation is expired. https://github.com/mini-bot/test-dev/invitations
/hold
/type xxx
@wuhuizuo: The label(s) type/xxx
cannot be applied, because the repository doesn't have them.
/retest
@mini-bot: 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 |
---|---|---|---|---|
prow_debug | 33a010c235e051b84d00857d3cf53f071c94cef0 | link | true | /test prow_debug |
/test all
@wuhuizuo: No presubmit jobs available for ti-community-infra/test-dev@release-5.2
/retest
/merge
@wuhuizuo: /merge
in this pull request requires 1 approval(s).
/unhold
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale
This is an automated cherry-pick of #528
What problem does this PR solve?
Issue Number: close #526
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
How it Works:
Check List
Tests
Side effects
Documentation
Release note