Skip to content

docs(feishu): document threadRequireMention + botName post #1534#1573

Merged
qin-ctx merged 2 commits intovolcengine:mainfrom
r266-tech:docs/feishu-thread-require-mention-post-1534
Apr 20, 2026
Merged

docs(feishu): document threadRequireMention + botName post #1534#1573
qin-ctx merged 2 commits intovolcengine:mainfrom
r266-tech:docs/feishu-thread-require-mention-post-1534

Conversation

@r266-tech
Copy link
Copy Markdown
Contributor

动机

#1534 (feat(bot): enhance Feishu mentions and name display) 2026-04-17 merge 后:

  1. thread_require_mention 开关的语义从"只作用于话题群"扩展为"同时作用于普通群和话题群"bot/vikingbot/channels/feishu.py _check_should_process 的控制流明确注释 "普通群和话题群都根据 thread_require_mention 判断";但 bot/docs/CHANNEL.md 的飞书配置示例不含此字段,bot/vikingbot/config/schema.py 中该 Field 的 description 仍写 "话题群模式下…",会误导用户以为普通群行为不变。
  2. bot_name 配置项在 feat(bot):enhance Feishu mentions and name display #1534 新增被 _get_bot_name 用作群聊上下文中机器人自身名称(空字符串回退为 "Bot"),CHANNEL.md 从未提及。

改动

两处纯文档/字段描述补齐,无行为改动:

  • bot/docs/CHANNEL.md — 飞书 <details> 段的配置示例新增 botName / threadRequireMention 两项,并在示例下方补两行说明(threadRequireMention 的说明包含 DEBUG 模式例外分支以避免误导)。
  • bot/vikingbot/config/schema.pythread_require_mention Field 的 description 改为反映 post-feat(bot):enhance Feishu mentions and name display #1534 的真实行为("普通群和话题群 … 非 DEBUG 模式下后续回复必须@")。

遵循 loader.py camel_to_snake 约定,JSON 侧用 camelCase。

测试

纯文档/描述字符串,无需新增测试。

相关

@github-actions
Copy link
Copy Markdown

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🏅 Score: 98
🧪 No relevant tests
🔒 No security concerns identified
✅ No TODO sections
🔀 No multiple PR themes
⚡ No major issues detected

@github-actions
Copy link
Copy Markdown

PR Code Suggestions ✨

No code suggestions found for the PR.

@qin-ctx qin-ctx merged commit f19ddf6 into volcengine:main Apr 20, 2026
6 checks passed
@github-project-automation github-project-automation Bot moved this from Backlog to Done in OpenViking project Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants