Skip to content

Update package.md#6293

Merged
LIghtJUNction merged 1 commit intomasterfrom
LIghtJUNction-patch-1
Mar 14, 2026
Merged

Update package.md#6293
LIghtJUNction merged 1 commit intomasterfrom
LIghtJUNction-patch-1

Conversation

@LIghtJUNction
Copy link
Copy Markdown
Member

@LIghtJUNction LIghtJUNction commented Mar 14, 2026

Modifications / 改动点

  • This is NOT a breaking change. / 这不是一个破坏性变更。

Screenshots or Test Results / 运行截图或测试结果


Checklist / 检查清单

  • 😊 如果 PR 中有新加入的功能,已经通过 Issue / 邮件等方式和作者讨论过。/ If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
  • 👀 我的更改经过了良好的测试,并已在上方提供了“验证步骤”和“运行截图”。/ My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
  • 🤓 我确保没有引入新依赖库,或者引入了新依赖库的同时将其添加到了 requirements.txtpyproject.toml 文件相应位置。/ I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in requirements.txt and pyproject.toml.
  • 😮 我的更改没有引入恶意代码。/ My changes do not introduce malicious code.

Summary by Sourcery

Documentation:

  • Adjust the Chinese deployment guide to instruct users to start AstrBot with astrbot run instead of the previous astrbot command.

@LIghtJUNction LIghtJUNction marked this pull request as ready for review March 14, 2026 18:55
Copilot AI review requested due to automatic review settings March 14, 2026 18:55
@gemini-code-assist
Copy link
Copy Markdown
Contributor

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 updates the Chinese deployment documentation for astrbot to ensure users are provided with the correct command for running the application. This minor correction improves the accuracy of the deployment instructions.

Highlights

  • Documentation Update: Corrected the astrbot command in the Chinese deployment guide from astrbot to astrbot run to accurately reflect the application's startup command.
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.

@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Mar 14, 2026
Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Copy Markdown
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 command to astrbot run in the Chinese documentation. I've provided a suggestion to further improve the clarity of the instructions. Additionally, I noticed that the corresponding English documentation in docs/en/deploy/astrbot/package.md still contains the outdated astrbot command and is missing the astrbot init step. It would be beneficial to update the English documentation as well to ensure consistency.

Comment on lines 13 to 17
```bash
uv tool install astrbot
astrbot init # 只需要在第一次部署时执行,后续启动不需要执行
astrbot
astrbot run
```
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For better clarity, consider separating the commands for the first-time setup and subsequent runs. The current inline comment is helpful, but explicitly structuring the document with separate sections for 'First-time deployment' and 'Subsequent starts' would make it easier for users to follow.

For example:

首次部署 (First-time deployment)

uv tool install astrbot
astrbot init
astrbot run

后续启动 (Subsequent starts)

astrbot run

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Chinese uv-based deployment guide to use the correct CLI subcommand for starting AstrBot after initialization, aligning the documentation with the current astrbot CLI behavior.

Changes:

  • Replace the outdated astrbot start command with astrbot run in the uv deployment instructions.
  • Keep the initialization step (astrbot init) explicitly documented as first-run only.

You can also share your feedback on Copilot code review. Take the survey.

@LIghtJUNction LIghtJUNction merged commit 96cafe0 into master Mar 14, 2026
10 checks passed
@LIghtJUNction LIghtJUNction deleted the LIghtJUNction-patch-1 branch March 14, 2026 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants