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

config: rename pingcap/ticdc to pingcap/tiflow #482

Merged
merged 3 commits into from
Dec 17, 2021

Conversation

amyangfei
Copy link
Contributor

@amyangfei amyangfei commented Dec 17, 2021

This is part job of step-4 in https://github.com/pingcap/ticdc/issues/3749

The change is triggered by:
sed -i "s/pingcap\/ticdc/pingcap\/tiflow/g" $(find . -type f)

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 17, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • Mini256

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 contribution This PR is from a community contributor. needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. labels Dec 17, 2021
@ti-chi-bot
Copy link
Member

Hi @amyangfei. Thanks for your PR.

I'm waiting for a ti-community-infra member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@ti-chi-bot ti-chi-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 17, 2021
@amyangfei
Copy link
Contributor Author

/ok-to-test

@ti-chi-bot
Copy link
Member

@amyangfei: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

@Mini256
Copy link
Member

Mini256 commented Dec 17, 2021

/ok-to-test

@ti-chi-bot ti-chi-bot added ok-to-test Indicates a PR is ready to be tested. and removed needs-ok-to-test Indicates a PR created by contributors and need ORG member send '/ok-to-test' to start testing. labels Dec 17, 2021
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 17, 2021
@Mini256
Copy link
Member

Mini256 commented Dec 17, 2021

/merge

@ti-chi-bot
Copy link
Member

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

Commit hash: 77891f1

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 17, 2021
@ti-chi-bot ti-chi-bot merged commit 1a31c57 into ti-community-infra:main Dec 17, 2021
@ti-chi-bot
Copy link
Member

@amyangfei: Updated the following 5 configmaps:

  • labels-config configmap in namespace prow at cluster default using the following files:
    • key labels.yaml using file prow/config/labels.yaml
  • plugins configmap in namespace prow at cluster default using the following files:
    • key plugins.yaml using file prow/config/plugins.yaml
  • job-config configmap in namespace prow at cluster default using the following files:
    • key configs-postsubmits.yaml using file prow/jobs/ti-community-infra/configs/configs-postsubmits.yaml
  • config configmap in namespace prow at cluster default using the following files:
    • key config.yaml using file prow/config/config.yaml
  • external-plugins-config configmap in namespace prow at cluster default using the following files:
    • key external_plugins_config.yaml using file prow/config/external_plugins_config.yaml

In response to this:

This is part job of step-4 in https://github.com/pingcap/ticdc/issues/3749

The change is triggered by:
sed -i "s/pingcap\/ticdc/pingcap\/tiflow/g" $(find . -type f)

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.

@amyangfei amyangfei deleted the rename-ticdc-to-tiflow branch December 17, 2021 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution This PR is from a community contributor. ok-to-test Indicates a PR is ready to be tested. 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/LGT1 Indicates that a PR has LGTM 1.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants