v8.5: add Serverless name change notice #21371
Conversation
lilin90
added
translation/no-need
ti-chi-bot
bot
added
the
area/develop
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
the
size/S
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @lilin90, 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 focuses on updating the TiDB Cloud documentation for version 8.5 to incorporate a recent name change for one of its cluster tiers. The primary goal is to ensure that all relevant user-facing content accurately reflects the new naming convention, providing clarity and avoiding confusion for users interacting with the platform.
Highlights
- Documentation Updates for Name Change: I've updated various documentation files to reflect the name change of the 'Serverless' cluster tier to '{{{ .starter }}}' within TiDB Cloud.
- Clarity on Cluster Tiers: I've added clarifying notices such as '(formerly Serverless)', '(now {{{ .starter }}})', or '(renamed to {{{ .starter }}})' alongside mentions of the 'Serverless' tier to guide users through the naming transition.
- Consistency in Quickstart Guides: I've ensured that quickstart and development guides consistently refer to the new '{{{ .starter }}}' cluster name where appropriate, replacing older 'TiDB Cloud Serverless cluster' references.
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.
Code Review
This PR updates documentation files to reflect the renaming of 'TiDB Cloud Serverless' to '{{{ .starter }}}'. To improve clarity and maintain consistency, I suggest using the same phrasing for the name change notice across all files. Also, ensure that the internal links are updated to point to the correct anchors after the heading changes.
lilin90
added
the
do-not-merge/hold
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
This PR adds Serverless name change notice to cloud related descriptions.
Note
The updates for
release-cloudare made in #21373.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?