cloud: update docs for lark support bot (#22425)

[ti-chi-bot]

This is an automated cherry-pick of #22425

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)

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.

• 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

[gemini-code-assist]

Summary of Changes

Hello @ti-chi-bot, 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 updates the documentation for the TiDB Cloud PingCAP Support Bot in Lark. The changes aim to provide clearer instructions and details regarding the creation of support tickets and the interaction with ticket updates, particularly highlighting the two-way synchronization capabilities for users on the Premium support plan.

Highlights

• Updated Ticket Creation Process: The documentation now provides clearer, step-by-step instructions for creating support tickets via the PingCAP Support Bot in Lark, including how to initiate the process and fill out the ticket card.
• Enhanced Ticket Update Clarity: The explanation for subscribing to and receiving ticket updates in Lark has been refined, detailing the information provided in the bot's update messages.
• Clarified Two-Way Ticket Interaction: The section on interacting with support tickets has been revised to emphasize the two-way synchronization of comments between Lark and the support system, specifically for users on the Premium support plan.

🧠 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

• tidb-cloud/connected-lark-ticket-creation.md
  • Refined the introductory description of the PingCAP Support Bot's functionality.
  • Restructured the "Create a support ticket" section with numbered steps and clearer instructions.
  • Added a new screenshot to illustrate the ticket creation confirmation.
  • Updated the "Subscribe to ticket updates" section with a more detailed explanation and a new screenshot.
• tidb-cloud/connected-lark-ticket-interaction.md
  • Completely rewrote the "Interact with support tickets" section to better explain the two-way synchronization feature for Premium plan users.
  • Removed outdated descriptions of message card conversion.
  • Introduced a new screenshot to demonstrate the updated ticket interaction flow.

Activity

• This pull request is an automated cherry-pick of update docs for lark support bot #22425.

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

[qiancai]

/approve

[ti-chi-bot]

[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

Details

Needs approval from an approver in each of these files:

• OWNERS [qiancai]

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

[gemini-code-assist]

Code Review

This pull request updates the documentation for Lark integration, improving the instructions for creating and interacting with support tickets. The changes align well with the repository's style guide by enhancing clarity, using ordered lists for procedures, and adopting a user-focused tone. I've added a couple of suggestions to further refine the clarity of the instructions and improve readability.