-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
tools: add a guide for choosing TiDB Ecosystem Tools #2210
Conversation
Co-Authored-By: Ian <ArGregoryIan@gmail.com>
…docs-cn into xiang/tools_guide
@GregoryIan all resolved, PTAL again |
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I made a commit to refine the doc. Preview here: https://github.com/pingcap/docs-cn/blob/a60684586926f195b801d7eb02e155679685b322/dev/reference/tools/use-guide.md PTAL @WangXiangUSTC NOTE: Because #2184 is still under review, a dead link appears because of my new commit. We should merge this PR after #2184 is merged. I'll push forward its progress as quickly as possible. |
#2184 is merged. Please update the other versions and we can merge this PR~ @WangXiangUSTC |
@yikeke v2.1, v3.0 and v3.1 is updated, PTAL again |
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
thanks @yikeke |
@toutdesuite Please also refer to related changes in #2244 when you deal with the English version. Pay attention to the new file name. Thanks! |
What is changed, added or deleted?
Now we have too many tools, users may don't know how to choose. So we need add a guide, tells users every tool's usage scenario.
Which TiDB version(s) does your changes apply to?
Note: If your changes apply to multiple TiDB versions, make sure you update the documents in the corresponding version folders such as "dev", "v3.0", "v2.1" and "v3.1" in this PR.