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

Add aliases to 500 files on master branch #4185

Merged
merged 4 commits into from
Aug 4, 2020
Merged

Add aliases to 500 files on master branch #4185

merged 4 commits into from
Aug 4, 2020

Conversation

yikeke
Copy link
Contributor

@yikeke yikeke commented Aug 4, 2020 •
edited
Loading

What is changed, added or deleted? (Required)

Add one alias to all files on master branch

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Have version specific changes
  • Might cause conflicts

@yikeke yikeke changed the title Add aliases to 503 files on master branch Add aliases to 502 files on master branch Aug 4, 2020
@yikeke yikeke changed the title Add aliases to 502 files on master branch Add aliases to 501 files on master branch Aug 4, 2020
@yikeke yikeke changed the title Add aliases to 501 files on master branch Add aliases to 500 files on master branch Aug 4, 2020
@yikeke yikeke requested review from YiniXu9506 and lilin90 August 4, 2020 06:26
@yikeke yikeke added the translation/no-need No need to translate this PR. label Aug 4, 2020
YiniXu9506
YiniXu9506 approved these changes Aug 4, 2020
View reviewed changes
Copy link
Contributor

@YiniXu9506 YiniXu9506 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-srebot ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Aug 4, 2020
@yikeke yikeke added the require-LGT1 Indicates that the PR requires an LGTM. label Aug 4, 2020
@yikeke
Copy link
Contributor Author

yikeke commented Aug 4, 2020

/merge

@ti-srebot ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Aug 4, 2020
@ti-srebot
Copy link
Contributor

/run-all-tests

@yikeke yikeke merged commit fb3847a into master Aug 4, 2020
@yikeke yikeke deleted the add-alias-to-dev branch August 4, 2020 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@YiniXu9506 YiniXu9506 YiniXu9506 approved these changes

@lilin90 lilin90 Awaiting requested review from lilin90

Assignees
No one assigned
Labels
require-LGT1 Indicates that the PR requires an LGTM. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. translation/no-need No need to translate this PR.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@yikeke @ti-srebot @YiniXu9506