8000 [skip e2e] Automated Update Cardinal Commit by sre-ci-robot · Pull Request #1197 · zilliztech/knowhere · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[skip e2e] Automated Update Cardinal Commit #1197

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[skip e2e] Automated Update Cardinal Commit #1197

wants to merge 1 commit into from

Conversation

sre-ci-robot
Copy link
Collaborator

Update Cardinal Commit
Signed-off-by: sre-ci-robot sre-ci-robot@users.noreply.github.com

@sre-ci-robot sre-ci-robot requested review from foxspy and hhy3 May 18, 2025 10:04
@sre-ci-robot
Copy link
Collaborator Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sre-ci-robot
To complete the pull request process, please assign zhengbuqian after the PR has been reviewed.
You can assign the PR to them by writing /assign @zhengbuqian in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mergify mergify bot added the dco-passed label May 18, 2025
@mergify Mergify
Copy link
mergify bot commented May 18, 2025

@sre-ci-robot 🔍 Important: PR Classification Needed!

For efficient project management and a seamless review process, it's essential to classify your PR correctly. Here's how:

  1. If you're fixing a bug, label it as kind/bug.
  2. For small tweaks (less than 20 lines without altering any functionality), please use kind/improvement.
  3. Significant changes that don't modify existing functionalities should be tagged as kind/enhancement.
  4. Adjusting APIs or changing functionality? Go with kind/feature.

For any PR outside the kind/improvement category, ensure you link to the associated issue using the format: “issue: #”.

Thanks for your efforts and contribution to the community!.

@mergify mergify bot mentioned this pull request May 18, 2025
Closed
@sre-ci-robot sre-ci-robot force-pushed the update_cardinal_commit_f79a358e66d7a61f5ec4aef5ecff3af6728be2e8 branch from 245f39f to 9910e93 Compare May 20, 2025 10:05
@sre-ci-robot sre-ci-robot force-pushed the update_cardinal_commit_f79a358e66d7a61f5ec4aef5ecff3af6728be2e8 branch from 9910e93 to 53330e1 Compare May 27, 2025 10:05
@sre-ci-robot sre-ci-robot force-pushed the update_cardinal_commit_f79a358e66d7a61f5ec4aef5ecff3af6728be2e8 branch from 53330e1 to 2e65711 Compare May 28, 2025 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@foxspy foxspy Awaiting requested review from foxspy

@hhy3 hhy3 Awaiting requested review from hhy3

At least 2 approving reviews are required to merge this pull request.

Assignees
No one assigned
Labels
ci-passed dco-passed do-not-merge/missing-related-issue size/XS
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@sre-ci-robot
0