docs: normalize QQ group listings in READMEs and community docs#6976
docs: normalize QQ group listings in READMEs and community docs#6976RC-CHN merged 2 commits intoAstrBotDevs:masterfrom
Conversation
dosubot
Bot
added
the
size:M
Summary of ChangesHello, 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 standardizes and updates the QQ group information across various documentation files, including internationalized READMEs and community pages. The changes ensure that all documentation consistently reflects the current QQ group availability, status, and proper formatting, providing users with accurate and up-to-date community engagement details. Highlights
Using Gemini Code AssistThe 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
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 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. Footnotes
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- In the English docs, the QQ group status labels are slightly inconsistent between
README.mdanddocs/en/community.md(e.g.,Group 9/10are marked(New)in the README but500-member group, recommendedin the community page); consider aligning the wording for all listed groups across these two entry points for clearer consistency.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In the English docs, the QQ group status labels are slightly inconsistent between `README.md` and `docs/en/community.md` (e.g., `Group 9/10` are marked `(New)` in the README but `500-member group, recommended` in the community page); consider aligning the wording for all listed groups across these two entry points for clearer consistency.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the QQ group lists across various language versions of the README.md and community.md files, adding new groups and reordering existing ones. A review comment suggests improving consistency in the Chinese documentation by changing half-width colons to full-width colons in docs/zh/community.md to align with formatting in other Chinese files.
| - 12 群: 916228568 (新) | ||
| - 9 群: 1076659624 (500 人群, 优先加此群) | ||
| - 10 群: 1078079676 (500 人群, 优先加此群) | ||
| - 11 群: 704659519 (人满) | ||
| - 1 群: 322154837 (2000 人群, 人满) | ||
| - 3 群: 630166526 (2000 人群, 人满) | ||
| - 4 群: 1077826412 (1000 人群, 人满) |
There was a problem hiding this comment.
For consistency with the formatting changes in README_zh.md and README_zh-TW.md, it's recommended to change the half-width colons (:) to full-width colons (：) in this list. This will help maintain a uniform typographic style across all Chinese documentation, aligning with the PR's goal to normalize formatting.
| - 12 群: 916228568 (新) | |
| - 9 群: 1076659624 (500 人群, 优先加此群) | |
| - 10 群: 1078079676 (500 人群, 优先加此群) | |
| - 11 群: 704659519 (人满) | |
| - 1 群: 322154837 (2000 人群, 人满) | |
| - 3 群: 630166526 (2000 人群, 人满) | |
| - 4 群: 1077826412 (1000 人群, 人满) | |
| - 12 群：916228568 (新) | |
| - 9 群：1076659624 (500 人群, 优先加此群) | |
| - 10 群：1078079676 (500 人群, 优先加此群) | |
| - 11 群：704659519 (人满) | |
| - 1 群：322154837 (2000 人群, 人满) | |
| - 3 群：630166526 (2000 人群, 人满) | |
| - 4 群：1077826412 (1000 人群, 人满) |
dosubot
Bot
added
size:L
|
@sourcery-ai review |
There was a problem hiding this comment.
Hey - I've found 1 issue, and left some high level feedback:
- The previous explanatory note about group capacity and joining (“All groups are available to join…”) was removed from both the Chinese and English community pages; consider restoring a short note so users understand that even ‘Full’ groups might occasionally accept new members or what ‘Full/New’ practically means.
- Status labels like “New/新/nouveau/новая” and “Full/人满/満員/полная” are now repeated across all locales; it may be worth double-checking that these translations match the project’s preferred terminology and tone for each language for long-term consistency.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The previous explanatory note about group capacity and joining (“All groups are available to join…”) was removed from both the Chinese and English community pages; consider restoring a short note so users understand that even ‘Full’ groups might occasionally accept new members or what ‘Full/New’ practically means.
- Status labels like “New/新/nouveau/новая” and “Full/人满/満員/полная” are now repeated across all locales; it may be worth double-checking that these translations match the project’s preferred terminology and tone for each language for long-term consistency.
## Individual Comments
### Comment 1
<location path="README_zh-TW.md" line_range="231" />
<code_context>
+- 6 群：753075035 (人滿)
+- 7 群：743746109 (人滿)
+- 8 群：1030353265 (人滿)
- 開發者群（闲聊吹水）：975206796
- 開發者群（正式）：1039761811
</code_context>
<issue_to_address>
**suggestion (typo):** Use a Traditional Chinese character here instead of the simplified `闲`.
This line mixes the simplified `闲` into otherwise Traditional Chinese text. For consistency with the `zh-TW` locale, please change `闲聊` to `閒聊`.
Suggested implementation:
```
- 開發者群（閒聊吹水）：975206796
```
目前提供的程式片段中只顯示到 `### QQ 群組` 前的群組列表，實際包含「開發者群（闲聊吹水）」這一行的區塊沒有完整展示。如果該行前後的格式或縮排與此搜尋字串不完全一致（例如多了空白、Tab 或是有 Markdown 清單符號差異），請依實際檔案內容微調 SEARCH 區塊以精確匹配原始行後再套用同樣的替換字串。
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| - 6 群：753075035 (人滿) | ||
| - 7 群：743746109 (人滿) | ||
| - 8 群：1030353265 (人滿) | ||
| - 開發者群（闲聊吹水）：975206796 |
There was a problem hiding this comment.
suggestion (typo): Use a Traditional Chinese character here instead of the simplified 闲.
This line mixes the simplified 闲 into otherwise Traditional Chinese text. For consistency with the zh-TW locale, please change 闲聊 to 閒聊.
Suggested implementation:
- 開發者群（閒聊吹水）：975206796
目前提供的程式片段中只顯示到 ### QQ 群組 前的群組列表，實際包含「開發者群（闲聊吹水）」這一行的區塊沒有完整展示。如果該行前後的格式或縮排與此搜尋字串不完全一致（例如多了空白、Tab 或是有 Markdown 清單符號差異），請依實際檔案內容微調 SEARCH 區塊以精確匹配原始行後再套用同樣的替換字串。
2 participants
Modifications / 改动点
completed the QQ group listings in the internationalized READMEs that previously missed several groups
added Group 11 (
704659519) with the full-status note and Group 12 (916228568) with the new-group note across the README/community entry pointsnormalized the QQ group list formatting in Chinese READMEs and aligned the ordering/style across README and community pages
updated the English community page to include Groups 9 and 10 so the main community entry points stay consistent
This is NOT a breaking change. / 这不是一个破坏性变更。
Screenshots or Test Results / 运行截图或测试结果
Verification Steps:
cd docs pnpm docs:buildResult:
Checklist / 检查清单
😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
/ 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。
👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
/ 我的更改经过了良好的测试，并已在上方提供了“验证步骤”和“运行截图”。
🤓 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.txtandpyproject.toml./ 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到
requirements.txt和pyproject.toml文件相应位置。😮 My changes do not introduce malicious code.
/ 我的更改没有引入恶意代码。
Summary by Sourcery
Documentation: