test: trigger ci test for 3.0

[feici02]

Auto PR for test/3.0-test-chr-2026-01-25

[gemini-code-assist]

Summary of Changes

Hello @feici02, 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 is an automatically generated PR intended solely to trigger the CI test suite for the 3.0 branch, specifically for the test/3.0-test-chr-2026-01-25 context. The code change itself is minimal and serves only to create a modification that prompts the CI system to run.

Highlights

• CI Trigger: This pull request is an automated trigger for the Continuous Integration (CI) pipeline, specifically targeting the 3.0 branch.
• Minimal Change: The only code modification is the addition of a blank line in CMakeLists.txt, serving purely to register a change and initiate the CI process.

🧠 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 introduces a line with trailing whitespace at the end of CMakeLists.txt and removes the final newline. My review includes a suggestion to remove this unnecessary line to maintain code cleanliness and adhere to standard file formatting conventions.

[gemini-code-assist]

This added line contains only whitespace and should be removed. It's also good practice to ensure files end with a single newline character.

[Copilot]

Pull request overview

This PR appears to be a no-op change intended to trigger CI for the 3.0 branch.

Changes:

• Adds a trailing whitespace-only line at the end of CMakeLists.txt.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Line adds a blank line that contains trailing whitespace. Please remove the extra spaces (leave a clean newline if you want a file-ending newline) to avoid introducing whitespace-only diffs and potential formatting/lint issues.

Suggested change

	message(STATUS "TAOSWS_GIT_TAG_NAME:${TAOSWS_GIT_TAG_NAME}")
	message(STATUS "TAOSWS_GIT_TAG_NAME:${TAOSWS_GIT_TAG_NAME}")