Skip to content

[Doc] docs(functions): update en, zh, ja documentation#66075

Open
Seaven wants to merge 3 commits intoStarRocks:mainfrom
Seaven:docs/update-functions-20251128-115617
Open

[Doc] docs(functions): update en, zh, ja documentation#66075
Seaven wants to merge 3 commits intoStarRocks:mainfrom
Seaven:docs/update-functions-20251128-115617

Conversation

@Seaven
Copy link
Contributor

@Seaven Seaven commented Nov 28, 2025

Why I'm doing:

What I'm doing:

EXECUTION SUMMARY
Document Type: functions
Duration: 7.58 seconds
Command: /home/seaven/documents/workspace/DocsAgent/src/docsagent/main.py -g -t functions --force_search_code -tv -n is_json_scalar --pr
Arguments:
  ├─ ci: False
  ├─ force_search_code: True
  ├─ generate: True
  ├─ include_miss_usage: False
  ├─ limit: None
  ├─ meta: False
  ├─ name: is_json_scalar
  ├─ pr: True
  ├─ track_version: True
  ├─ type: functions
  ├─ without_llm: False

ITEM EXTRACTION:
  ├─ Items from meta files: 316
  ├─ Items from code parsing: 0
  └─ Total unique items: 0

DOCUMENT GENERATION:
  └─ Total: 0 documents

This Pr is generated by DocsAgent

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 4.1
    • 4.0
    • 3.5
    • 3.4
    • 3.3

@Seaven Seaven requested a review from a team as a code owner November 28, 2025 03:56
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Nov 28, 2025
@mergify mergify bot assigned Seaven Nov 28, 2025
Signed-off-by: Seaven <seaven_7@qq.com>
@Seaven Seaven force-pushed the docs/update-functions-20251128-115617 branch from 8211604 to c33a594 Compare November 28, 2025 04:02
@Seaven Seaven changed the title [Doc] docs(functions): update en, zh, ja documentation [UT] docs(functions): update en, zh, ja documentation Nov 28, 2025
@Seaven Seaven changed the title [UT] docs(functions): update en, zh, ja documentation [DOC] docs(functions): update en, zh, ja documentation Nov 28, 2025
@Seaven Seaven changed the title [DOC] docs(functions): update en, zh, ja documentation [Doc] docs(functions): update en, zh, ja documentation Nov 28, 2025
@github-actions
Copy link
Contributor

🌎 Translation Required?

All translation files are up to date.
Great job! No translation actions are required for this PR.

🕒 Last updated: Thu, 19 Feb 2026 15:56:24 GMT

@github-actions
Copy link
Contributor

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

@github-actions
Copy link
Contributor

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

@github-actions
Copy link
Contributor

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-maintainer documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments