Skip to content
New issue

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

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

Already on GitHub? # to your account

OWNERS: Auto Sync OWNERS files from community membership #8163

Merged
merged 3 commits into from
May 29, 2024

Conversation

ti-chi-bot
Copy link
Member

Check List

Tests

  • No need to test
    • I checked and no code files have been changed.

skip-checks: true
Signed-off-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Copy link
Contributor

ti-chi-bot bot commented May 9, 2024

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • overvenus
  • purelind

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 bot added do-not-merge/needs-linked-issue do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels May 9, 2024
@ti-chi-bot ti-chi-bot bot requested review from HuSharp and nolouch May 9, 2024 09:41
@ti-chi-bot ti-chi-bot bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 9, 2024
@ti-chi-bot
Copy link
Member Author

/release-note-none

@ti-chi-bot ti-chi-bot added approved lgtm skip-issue-check Indicates that a PR no need to check linked issue. labels May 9, 2024
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/needs-linked-issue do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels May 9, 2024
@wuhuizuo
Copy link
Contributor

Ref #8167

@wuhuizuo
Copy link
Contributor

please ignore the failed CI job: idc-jenkins-ci/build_release, it's deprecated and disabled.

Copy link

codecov bot commented May 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.28%. Comparing base (b7d8b94) to head (467c5e2).

Current head 467c5e2 differs from pull request most recent head c33ce91

Please upload reports for the commit c33ce91 to get more accurate results.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8163      +/-   ##
==========================================
- Coverage   77.37%   77.28%   -0.10%     
==========================================
  Files         471      471              
  Lines       61339    61445     +106     
==========================================
+ Hits        47461    47487      +26     
- Misses      10313    10397      +84     
+ Partials     3565     3561       -4     
Flag Coverage Δ
unittests 77.28% <ø> (-0.10%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@wuhuizuo
Copy link
Contributor

/cc niubell

Copy link
Contributor

ti-chi-bot bot commented May 27, 2024

@wuhuizuo: GitHub didn't allow me to request PR reviews from the following users: niubell.

Note that only tikv members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc niubell

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.

Copy link
Contributor

ti-chi-bot bot commented May 28, 2024

@niubell: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

In response to this:

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.

Copy link
Contributor

@purelind purelind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ti-chi-bot ti-chi-bot bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 29, 2024
@ti-chi-bot ti-chi-bot bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels May 29, 2024
@purelind
Copy link
Contributor

/merge

Copy link
Contributor

ti-chi-bot bot commented May 29, 2024

@purelind: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and 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.

If you have any questions about the PR merge process, please refer to pr process.

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.

Copy link
Contributor

ti-chi-bot bot commented May 29, 2024

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

Commit hash: 467c5e2

@ti-chi-bot ti-chi-bot bot added the status/can-merge Indicates a PR has been approved by a committer. label May 29, 2024
Copy link
Contributor

ti-chi-bot bot commented May 29, 2024

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

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 bot merged commit 4820bc5 into master May 29, 2024
16 checks passed
@rleungx rleungx deleted the bot/update-owners-1715247673602 branch May 29, 2024 10:12
@wuhuizuo
Copy link
Contributor

/cherry-pick release-6.1
/cherry-pick release-6.5
/cherry-pick release-7.1
/cherry-pick release-7.5
/cherry-pick release-8.1

@ti-chi-bot
Copy link
Member Author

@wuhuizuo: new pull request created to branch release-6.1: #8271.

In response to this:

/cherry-pick release-6.1
/cherry-pick release-6.5
/cherry-pick release-7.1
/cherry-pick release-7.5
/cherry-pick release-8.1

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
Copy link
Member Author

@wuhuizuo: new pull request created to branch release-6.5: #8272.

In response to this:

/cherry-pick release-6.1
/cherry-pick release-6.5
/cherry-pick release-7.1
/cherry-pick release-7.5
/cherry-pick release-8.1

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
Copy link
Member Author

@wuhuizuo: new pull request created to branch release-7.1: #8273.

In response to this:

/cherry-pick release-6.1
/cherry-pick release-6.5
/cherry-pick release-7.1
/cherry-pick release-7.5
/cherry-pick release-8.1

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
Copy link
Member Author

@wuhuizuo: new pull request created to branch release-7.5: #8274.

In response to this:

/cherry-pick release-6.1
/cherry-pick release-6.5
/cherry-pick release-7.1
/cherry-pick release-7.5
/cherry-pick release-8.1

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
Copy link
Member Author

@wuhuizuo: new pull request created to branch release-8.1: #8275.

In response to this:

/cherry-pick release-6.1
/cherry-pick release-6.5
/cherry-pick release-7.1
/cherry-pick release-7.5
/cherry-pick release-8.1

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 bot pushed a commit that referenced this pull request Jun 11, 2024
 

Signed-off-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this pull request Jun 11, 2024
 

Signed-off-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this pull request Jun 11, 2024
 

Signed-off-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this pull request Jun 11, 2024
 

Signed-off-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this pull request Jun 11, 2024
 

Signed-off-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. skip-issue-check Indicates that a PR no need to check linked issue. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants