Skip to content

update some desc about auto-analyze#8859

Merged
ti-chi-bot[bot] merged 10 commits into
pingcap:masterfrom
glkappe:patch-101
May 17, 2023
Merged

update some desc about auto-analyze#8859
ti-chi-bot[bot] merged 10 commits into
pingcap:masterfrom
glkappe:patch-101

Conversation

@glkappe
Copy link
Copy Markdown
Contributor

@glkappe glkappe commented Apr 6, 2022 •
edited
Loading

update some desc and format about auto-analyze, please

First-time contributors' checklist

What is changed, added or deleted? (Required)

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

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v6.0 (TiDB 6.0 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)
  • 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
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@glkappe
update some desc about auto-analyze
63f795f 
update some desc and format about auto-analyze, please
@ti-chi-bot
Copy link
Copy Markdown
Member

ti-chi-bot commented Apr 6, 2022 •
edited by ti-chi-bot Bot
Loading

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • qiancai

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.

Details

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 requested a review from TomShawn April 6, 2022 04:01
@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 6, 2022
TomShawn
TomShawn reviewed Apr 6, 2022
View reviewed changes
Comment thread statistics.md Outdated
TomShawn
TomShawn reviewed Apr 6, 2022
View reviewed changes
Comment thread statistics.md Outdated
TomShawn
TomShawn reviewed Apr 6, 2022
View reviewed changes
Comment thread statistics.md Outdated
TomShawn
TomShawn reviewed Apr 6, 2022
View reviewed changes
Comment thread statistics.md Outdated
TomShawn
TomShawn reviewed Apr 6, 2022
View reviewed changes
Comment thread statistics.md Outdated
@TomShawn TomShawn self-assigned this Apr 6, 2022
@TomShawn TomShawn added type/enhancement The issue or PR belongs to an enhancement. translation/doing This PR’s assignee is translating this PR. area/planner Indicates that the Issue or PR belongs to the area of SQL planner or optimizer. needs-cherry-pick-release-6.0 and removed missing-translation-status This PR does not have translation status info. labels Apr 6, 2022
@TomShawn TomShawn added the needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. label Jun 7, 2022
@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 24, 2022
@TomShawn TomShawn added the needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. label Dec 28, 2022
@qiancai
Copy link
Copy Markdown
Collaborator

qiancai commented Feb 24, 2023

Removed the needs-cherry-pick-release-6.3 label because the v6.3 docs have been archived at https://docs-archive.pingcap.com/zh/tidb/v6.3 and will no longer receive new updates.

@lilin90
Copy link
Copy Markdown
Member

lilin90 commented Mar 30, 2023

@glkappe Would you please address the comments?

@ti-chi-bot ti-chi-bot Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 8, 2023
@qiancai qiancai removed needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-6.6 labels May 8, 2023
@ti-chi-bot ti-chi-bot Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 9, 2023
@ti-chi-bot ti-chi-bot Bot deleted a comment from ti-chi-bot May 9, 2023
@ti-chi-bot ti-chi-bot Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 9, 2023
@ti-chi-bot ti-chi-bot Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 9, 2023
@glkappe
Copy link
Copy Markdown
Contributor Author

glkappe commented May 10, 2023

/LGTM

@ti-chi-bot ti-chi-bot Bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 11, 2023
qiancai
qiancai reviewed May 11, 2023
View reviewed changes
Comment thread statistics.md Outdated
@qiancai qiancai mentioned this pull request May 11, 2023
Merged
17 tasks
@qiancai
Copy link
Copy Markdown
Collaborator

qiancai commented May 17, 2023

/merge

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot Bot commented May 17, 2023

@qiancai: /merge in this pull request requires 2 approval(s).

Details

In response to this:

/merge

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 ti-community-infra/tichi repository.

@qiancai
Copy link
Copy Markdown
Collaborator

qiancai commented May 17, 2023

/remove-status LGT1
/status LGT2
/merge

@ti-chi-bot ti-chi-bot Bot added the status/LGT2 Indicates that a PR has LGTM 2. label May 17, 2023
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot Bot commented May 17, 2023

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

DetailsCommit hash: afdbd8e

@ti-chi-bot ti-chi-bot Bot added status/can-merge Indicates a PR has been approved by a committer. and removed status/LGT1 Indicates that a PR has LGTM 1. labels May 17, 2023
@ti-chi-bot ti-chi-bot Bot merged commit 7f9c014 into pingcap:master May 17, 2023
@qiancai qiancai added translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. and removed translation/doing This PR’s assignee is translating this PR. labels May 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@qiancai qiancai qiancai approved these changes

+2 more reviewers

@TomShawn TomShawn TomShawn left review comments

@xuyifangreeneyes xuyifangreeneyes xuyifangreeneyes approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@qiancai qiancai

Labels

area/planner Indicates that the Issue or PR belongs to the area of SQL planner or optimizer. size/S Denotes a PR that changes 10-29 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. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. type/enhancement The issue or PR belongs to an enhancement.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@glkappe @ti-chi-bot @qiancai @lilin90 @xuyifangreeneyes @TomShawn