-
Notifications
You must be signed in to change notification settings - Fork 701
master: use a variable to refer to TiDB Cloud Serverless #21323
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
Conversation
Skipping CI for Draft Pull Request. |
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.
Summary of Changes
Hello @Oreoxmt, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request is a documentation maintenance effort aimed at improving the long-term consistency and maintainability of the project's documentation. It centralizes the reference to 'TiDB Cloud Serverless' by replacing its literal string with a templating variable, streamlining future updates across a wide range of files.
Highlights
- Documentation Standardization: I've replaced all hardcoded instances of 'TiDB Cloud Serverless' with the
{{{ .starter }}}
variable across numerous documentation files. This change specifically targets files outside thetidb-cloud
directory, as indicated in the PR description. - Improved Maintainability: By introducing a variable for the product name, future updates or renamings of 'TiDB Cloud Serverless' can be managed from a single point, significantly reducing the effort and potential for inconsistencies that manual string replacements would entail.
- Enhanced Consistency: This standardization ensures that the product name is consistently rendered throughout the affected documentation, improving clarity and accuracy for readers.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This PR aims to replace hardcoded references to 'TiDB Cloud Serverless' with the {{{ .starter }}}
variable for easier maintenance. The changes look good and are applied consistently across a large number of files.
I've left a few minor comments:
- A few suggestions to update link texts for consistency.
- One question to clarify a change from 'Serverless' to 'Starter' in one of the documents.
Overall, this is a solid and helpful refactoring. Thanks for the contribution!
|
||
1. If you do not have a TiDB Cloud account, click [here](https://tidbcloud.com/free-trial) to sign up for an account. | ||
|
||
2. [Log in](https://tidbcloud.com/) to your TiDB Cloud account. | ||
|
||
3. On the [**Clusters**](https://tidbcloud.com/console/clusters) page, click **Create Cluster**. | ||
|
||
4. On the **Create Cluster** page, **Serverless** is selected by default. Update the default cluster name if necessary, and then select the region where you want to create your cluster. | ||
4. On the **Create Cluster** page, **Starter** is selected by default. Update the default cluster name if necessary, and then select the region where you want to create your cluster. <!-- TODO --> |
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.
I see you've changed Serverless
to Starter
here and added a <!-- TODO -->
comment. Could you please confirm if this change is intentional and correct? The PR description focuses on replacing TiDB Cloud Serverless
with the {{{ .starter }}}
variable, but this seems to be a different kind of update. If Starter
is the new term for the UI, this is fine, but I wanted to double-check.
@@ -25,7 +25,7 @@ To complete this tutorial, you need: | |||
|
|||
**If you don't have a TiDB Cloud Serverless cluster, you can create one as follows:** | |||
|
|||
- [Create a TiDB Cloud Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-cloud-serverless-cluster) | |||
- [Create a TiDB Cloud Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-cloud-cluster) |
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.
For consistency with the other changes in this PR, the link text here should also use the {{{ .starter }}}
variable.1
Style Guide References
- [Create a TiDB Cloud Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-cloud-cluster) | |
- [Create a {{{ .starter }}} cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-cloud-cluster) |
Footnotes
[LGTM Timeline notifier]Timeline:
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
First-time contributors' checklist
What is changed, added or deleted? (Required)
This PR uses the {{{ .starter }}} variable to replace TiDB Cloud Serverless to simplify maintenance.
This PR is only for files outside the tidb-cloud folder.
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?