chore: migrate to new prow reviewing

[wuhuizuo]

• Backgroup: https://internals.tidb.io/t/topic/854
• Ref: REQUEST: add prow OWNERS file to these repos and make prow config changes ti-community-infra/configs#824

Signed-off-by: wuhuizuo [email protected]

What problem does this PR solve?

Issue Number: ref ti-community-infra/configs#824

What is changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tiup:
• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[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.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

Hi @wuhuizuo. Thanks for your PR.

I'm waiting for a tikv 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.

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/test-infra repository.

[JmPotato]

Why not keep the original term committer?

[wuhuizuo]

It's talked in https://internals.tidb.io/t/topic/854.

[wuhuizuo]

Current it should not merged before all the other jobs be done, I will add a hold label to block it to merge, but we can give it a LGTM and /merge when we reach an agreement.

[nolouch]

+1, commiter is a more common term.

[wuhuizuo]

It's a struct field, we could consider it equal to our commiter.
https://www.kubernetes.dev/docs/guide/owners/#owners

[wuhuizuo]

/hold it should merge after the bot's config updated.

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456, multiple issues should use full syntax for each issue and be separated by a comma, like: Issue Number: close #123, ref #456.

_{📖 For more info, you can check the "Linking issues" section in the CONTRIBUTING.md.}

[wuhuizuo]

Ref: tikv/tikv#14513
close it.