Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.github: update the default label #4621

Merged
merged 15 commits into from
Feb 23, 2022
Merged

.github: update the default label #4621

merged 15 commits into from
Feb 23, 2022

Conversation

lance6716
Copy link
Contributor

@lance6716 lance6716 commented Feb 17, 2022

What problem does this PR solve?

Issue Number: ref #4287

What is changed and how it works?

The old subject/* doesn't satisfy check-issue-triage-complete

Check List

Tests

  • No code

Code changes

Side effects

Related changes

Release note

`None`.

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Feb 17, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • hi-rustin

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 ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 17, 2022
@lance6716 lance6716 added the require-LGT1 Indicates that the PR requires an LGTM. label Feb 17, 2022
@lance6716
Copy link
Contributor Author

/cc @hi-rustin

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Feb 17, 2022
@Rustin170506
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: a7d1806

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Feb 17, 2022
@lance6716
Copy link
Contributor Author

/run-integration-test

2 similar comments
@lance6716
Copy link
Contributor Author

/run-integration-test

@lance6716
Copy link
Contributor Author

/run-integration-test

@maxshuang
Copy link
Contributor

/run-integration-test /tikv=pr/11967

2 similar comments
@maxshuang
Copy link
Contributor

/run-integration-test /tikv=pr/11967

@maxshuang
Copy link
Contributor

/run-integration-test /tikv=pr/11967

@lance6716
Copy link
Contributor Author

/run-kafka-integration-test /tidb=pr/32434
/run-integration-test /tidb=pr/32434

@lance6716
Copy link
Contributor Author

/run-kafka-integration-test /tidb=pr/32434

@lance6716
Copy link
Contributor Author

/merge

@lance6716
Copy link
Contributor Author

/run-integration-test /tidb=pr/32434

@lance6716
Copy link
Contributor Author

/run-leak-test

@lance6716
Copy link
Contributor Author

/run-kafka-integration-test /tidb=pr/32434
/run-leak-test

@maxshuang
Copy link
Contributor

/run-integration-test

@maxshuang
Copy link
Contributor

/run-integration-test /tidb=pr/32434

@ti-chi-bot
Copy link
Member

@lance6716: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.

@ti-chi-bot ti-chi-bot merged commit 2a15bb1 into master Feb 23, 2022
@overvenus overvenus deleted the lance6716-patch-1 branch April 19, 2022 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. require-LGT1 Indicates that the PR requires an LGTM. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants