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

chore: update codes import #1109

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

chore: update codes import #1109

wants to merge 2 commits into from

Conversation

wk989898
Copy link
Collaborator

What problem does this PR solve?

Issue Number: close #xxx

What is changed and how it works?

Check List

Tests

  • Unit test
  • Integration test

Questions

Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`None`.

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-linked-issue release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 14, 2025
Copy link

ti-chi-bot bot commented Mar 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongyunyan

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

The pull request process is described 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

@ti-chi-bot ti-chi-bot bot added the lgtm label Mar 14, 2025
Copy link

ti-chi-bot bot commented Mar 14, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-03-14 08:32:35.081009384 +0000 UTC m=+517510.686538311: ☑️ agreed by hongyunyan.

@ti-chi-bot ti-chi-bot bot added the approved label Mar 14, 2025
Copy link

ti-chi-bot bot commented Mar 14, 2025

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

📖 For more info, you can check the "Contribute Code" section in the development guide.

@wk989898
Copy link
Collaborator Author

/retest

1 similar comment
@wk989898
Copy link
Collaborator Author

/retest

@wk989898
Copy link
Collaborator Author

/test pull-cdc-mysql-integration-light

2 similar comments
@wk989898
Copy link
Collaborator Author

/test pull-cdc-mysql-integration-light

@wk989898
Copy link
Collaborator Author

/test pull-cdc-mysql-integration-light

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants