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

update auto-random.md (#2811) #2820

Closed

Conversation

sre-bot
Copy link
Contributor

@sre-bot sre-bot commented Jun 12, 2020

cherry-pick #2811 to release-3.0


What is changed, added or deleted? (Required)

Update auto-random.md.

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)

If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-4.0, needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.

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

Signed-off-by: sre-bot <sre-bot@pingcap.com>
@sre-bot sre-bot mentioned this pull request Jun 12, 2020
5 tasks
@sre-bot sre-bot added the type/cherry-pick-for-release-3.0 This PR is cherry-picked to release-3.0 from a source PR. label Jun 12, 2020
@sre-bot sre-bot requested review from tangenta and yikeke June 12, 2020 05:40
@ran-huang
Copy link
Contributor

@tangenta Hi, I don't see the Chinese version in v3.0.
Is auto-random.md applicable to v3.0?

@tangenta
Copy link
Contributor

@tangenta Hi, I don't see the Chinese version in v3.0.
Is auto-random.md applicable to v3.0?

@ran-huang No, v3.0 does not support auto_random.

@ran-huang ran-huang closed this Jun 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/cherry-pick-for-release-3.0 This PR is cherry-picked to release-3.0 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants