Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: update activation doc#34659

Open
danielclow wants to merge 3 commits intomainfrom
docs/update-activation-doc
Open

docs: update activation doc#34659
danielclow wants to merge 3 commits intomainfrom
docs/update-activation-doc

Conversation

@danielclow
Copy link
Contributor

@danielclow danielclow commented Mar 3, 2026

add root user requirement and CLI procedure

@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Mar 3, 2026

Summary of Changes

Hello, 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 enhances the TDengine TSDB-Enterprise activation documentation by incorporating detailed command-line interface (CLI) procedures and clarifying the necessity of root user privileges for these operations. The changes aim to provide more comprehensive and user-friendly guidance for activating licenses, accommodating different user preferences for activation methods.

Highlights

  • Root User Requirement: Explicitly added the requirement to use the root user for CLI operations related to activation, ensuring proper permissions.
  • CLI Activation Procedure: Introduced a new section detailing how to obtain an activation code and activate the deployment using the TDengine CLI, providing an alternative to the GUI.
  • Tabbed Interface for Activation: Refactored the activation steps into a tabbed interface, providing separate, clear instructions for both TDengine CLI and TDengine TSDB Explorer methods.

🧠 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
  • docs/en/08-operation/30-activate.md
    • Added Docusaurus Tabs, TabItem, and Enterprise components for improved content organization.
    • Inserted a new subsection "Obtain Your Activation Code" with instructions for using the taos CLI as the root user.
    • Restructured the "Activate Your Deployment" section to use a tabbed layout, separating CLI-based activation from TSDB Explorer-based activation.
    • Included ALTER CLUSTER command for CLI activation and SHOW GRANTS for license verification.
    • Updated TSDB Explorer instructions to specify root user login and added an important note about activation code formatting.
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. ↩

@taosdata-bot taosdata-bot bot added the internal label Mar 3, 2026
gemini-code-assist[bot]
gemini-code-assist bot reviewed Mar 3, 2026
View reviewed changes
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for activating TDengine Enterprise. It adds a clear distinction between CLI and TSDB Explorer activation methods, and correctly marks this as an Enterprise feature. My review focuses on improving the clarity and correctness of the documentation. I've pointed out several places where list numbering should be sequential for better readability and a minor typo. Overall, these changes make the activation process easier to follow.

Note: Security Review has been skipped due to the limited scope of the PR.

danielclow and others added 2 commits March 3, 2026 10:11
@danielclow
fix lint
98677ad
@danielclow @gemini-code-assist
Update docs/en/08-operation/30-activate.md
b64ea44 
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@guanshengliang guanshengliang Awaiting requested review from guanshengliang guanshengliang is a code owner

@zitsen zitsen Awaiting requested review from zitsen zitsen is a code owner

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

internal

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@danielclow