one console: replace cluster with instance for Starter and Essential#22542
Conversation
|
Warning Gemini encountered an error creating the summary. You can try again by commenting |
735daaf to
7258fdb
Compare
66e7a50 to
cbd8e1a
Compare
|
/gemini review |
|
/gemini summary |
There was a problem hiding this comment.
Code Review
The pull request primarily focuses on a comprehensive terminology update across various documentation files. This involves consistently replacing terms like "cluster" with "instance" or "resource" to better reflect different TiDB Cloud deployment models (Starter/Essential instances vs. Dedicated clusters) and to simplify language. The review comments suggest further improvements for clarity by retaining specific UI element names in dialog box titles and ensuring the completeness of information, such as re-including the prerequisite about TiFlash nodes for vector indexes.
Summary of ChangesThis pull request focuses on a comprehensive terminology update across the documentation, primarily changing references from 'cluster' to 'instance' for TiDB Cloud's Starter and Essential plans. This change aims to provide a more accurate and consistent user experience, particularly within the console's navigation and various feature descriptions. The updates span across quick start guides, AI/ML documentation, GUI tool integration instructions, and technical reference materials, ensuring that users encounter unified terminology when interacting with TiDB Cloud resources. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
|
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
| You can get these connection parameters from the [TiDB Cloud console](https://tidbcloud.com) as follows: | ||
|
|
||
| 1. Navigate to the [**Clusters**](https://tidbcloud.com/project/clusters) page, and then click the name of your target cluster to go to its overview page. | ||
| 1. Navigate to the [**My TiDB**](https://tidbcloud.com/tidbs) page, and then click the name of your target {{{ .starter }}} or Essential instance to go to its overview page. |
There was a problem hiding this comment.
Yes, although there is a var called .essential, we use “{{{ .starter }}} or Essential” here instead of “{{{ .starter }}} or {{{ .essential }}}” to reduce redundancy and improve readability.
Co-authored-by: awxxxxxx <7347183+awxxxxxx@users.noreply.github.com>
Co-authored-by: awxxxxxx <7347183+awxxxxxx@users.noreply.github.com>
[LGTM Timeline notifier]Timeline:
|
|
/retest |
|
@awxxxxxx: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this:
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-sigs/prow repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
c904a6b
into
pingcap:feature/preview-one-console
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?