Skip to content

fix: use isGroupMessage for replyTo, consistent with allowlist logic #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
LinekForge merged 2 commits into from
May 8, 2026
Merged

fix: use isGroupMessage for replyTo, consistent with allowlist logic #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b7f4c9
fix: use isGroupMessage for replyTo, consistent with allowlist logic
May 8, 2026
a372ecd
chore: ignore bun.lock (local-generated, not tracked upstream)
May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ dist/
.env.local
*.local.json
*.bak.*
bun.lock

# Test output
/tmp/
Expand Down
2 changes: 1 addition & 1 deletion hub-server/channels/feishu.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,7 +265,7 @@ async function handleMessage(event: Record<string, unknown>): Promise<void> {
hub.log(`← ${displayName}: ${content.slice(0, 80)}${content.length > 80 ? "..." : ""}`);

// 群消息用 chat_id (oc_) 作为 fromId，这样 reply 会发到群里而不是私聊
const replyTo = chatId.startsWith("oc_") ? chatId : senderId;
const replyTo = isGroupMessage ? chatId : senderId;
hub.pushMessage({
channel: "feishu",
from: displayName,
Expand Down