cloud: make community access visible and accurate in connected care relevant…

[April-Xu]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Streamline the "Working with Support Team", "Connected Care Overview", and "Connected Care Details" documentation to provide clearer guidance on support channel policies and community access.

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

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hfxsd for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Welcome @April-Xu!

It looks like this is your first PR to pingcap/docs 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs. 😃

[ti-chi-bot]

Hi @April-Xu. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[pingcap-cla-assistant]

All committers have signed the CLA.

[gemini-code-assist]

Summary of Changes

Hello @April-Xu, I'm Gemini Code Assist¹! 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 enhancing the clarity and accuracy of TiDB Cloud's support documentation. The changes streamline information regarding various support channels, explicitly detail community access for different service plans, and ensure consistent terminology across related documents. The primary goal is to make it easier for users to understand their support options and effectively utilize community resources like Slack and Discord for assistance.

Highlights

• Navigation Update: The 'Get Support' navigation link has been renamed to 'Working with Support Team' across all TiDB Cloud documentation tables of contents (TOC-tidb-cloud-essential.md, TOC-tidb-cloud-premium.md, TOC-tidb-cloud-starter.md, TOC-tidb-cloud.md) for improved clarity.
• Community Access Clarity: Descriptions for Developer and Basic plans in the 'Connected Care Overview' document now explicitly include direct links to TiDB Community Slack and Discord, making community resources more discoverable.
• Detailed Support Channels Section: A new 'Support Channels' section has been introduced in the 'Connected Care Overview' document, providing a comprehensive outline of available support avenues: Support Tickets, Community, and TiDB.AI, along with their respective uses.
• Support Document Refinement: The tidb-cloud-support.md document has been updated to reflect the new 'Working with Support Team' title and includes clarification that Basic plan users can seek technical assistance through community channels, as technical support tickets are reserved for paid plans.
• Community Workspace Links: The 'Connected Care Details' document now replaces generic 'Community Workspace' table entries with specific, clickable links to the TiDB Community Slack and Discord, enhancing direct access.

🧠 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.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

1. 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. ↩

[gemini-code-assist]

Code Review

This pull request effectively streamlines the documentation for TiDB Cloud support services, enhancing clarity around support channels and community access. The updates to rename 'Get Support' to 'Working with Support Team' and add direct links to community platforms are great improvements. I've provided a few minor suggestions to further align the text with the repository's style guide, primarily focusing on using the second-person perspective, active voice, and improving conciseness.

[hfxsd]

/ok-to-test

[MarianZhang00]

LGTM

[ti-chi-bot]

@MarianZhang00: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

LGTM

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.