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.

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

github: replace pingcap/ticdc with pingcap/tiflow in workflow (#3965) #3976

Merged
merged 2 commits into from
Feb 18, 2022
Merged

github: replace pingcap/ticdc with pingcap/tiflow in workflow (#3965) #3976

merged 2 commits into from
Feb 18, 2022

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #3965

What problem does this PR solve?

Some remaining pingcap/ticdc, finished the remaining problem-2 in #3749

The DM github action tests are verified in #3966.

These files were introduced from v5.3.0, so cherry pick to release-5.3 is enough.

What is changed and how it works?

replace pingcap/ticdc with pingcap/tiflow in files from .github dir

Check List

Tests

  • Unit test
  • Integration test
None

@ti-chi-bot
Copy link
Member Author

[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 ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/cherry-pick-not-approved size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-5.3 This PR is cherry-picked to release-5.3 from a source PR. labels Dec 20, 2021
@ti-chi-bot ti-chi-bot mentioned this pull request Dec 20, 2021
Merged
@amyangfei amyangfei force-pushed the cherry-pick-3965-to-release-5.3 branch from abb49fc to 136321c Compare December 20, 2021 05:44
@amyangfei
Copy link
Contributor

/run-all-tests

@overvenus overvenus added this to the v5.3.1 milestone Jan 6, 2022
@lichunzhu
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member Author

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

Commit hash: 136321c

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

/run-all-tests

@zhouqiang-cl zhouqiang-cl added the cherry-pick-approved Cherry pick PR approved by release team. label Feb 18, 2022
@lichunzhu
Copy link
Contributor

/run-all-tests

@ti-chi-bot ti-chi-bot merged commit f8de43e into pingcap:release-5.3 Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@lichunzhu lichunzhu lichunzhu approved these changes

@lance6716 lance6716 lance6716 approved these changes

Assignees

@amyangfei amyangfei

Labels
cherry-pick-approved Cherry pick PR approved by release team. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-5.3 This PR is cherry-picked to release-5.3 from a source PR.
Projects
None yet
Milestone
v5.3.1
Development

Successfully merging this pull request may close these issues.
6 participants
@ti-chi-bot @amyangfei @lichunzhu @lance6716 @overvenus @zhouqiang-cl