feat: mention Feishu user in issue notification card#13199
Merged
Conversation
Add @mention for Feishu user (cli_a92d6e7ba3f85ced) in the issue notification card body, so the user gets notified in Feishu when a new GitHub issue is processed. Co-Authored-By: Claude Opus 4.6 <[email protected]>
EurFelux
approved these changes
Mar 4, 2026
GeorgeDong32
approved these changes
Mar 4, 2026
6 tasks
DeJeune
added a commit
that referenced
this pull request
Mar 4, 2026
### What this PR does Before this PR: Attempted to add Feishu @mention notifications in issue cards using `<at id=...></at>` tags with various ID formats (app ID, open_id). After this PR: Reverted all mention-related changes. The Feishu card content is restored to its original state without @mention tags. ### Why we need it and why it was done in this way Testing confirmed that while the `<at>` tag with open_id displays correctly in the card, Feishu does not provide a message receive API for bots — so bot users cannot actually receive @mention notifications. The feature is not feasible with the current Feishu API capabilities. ### Breaking changes None ### Special notes for your reviewer This PR reverts the mention feature added in #13199 and all subsequent test commits. Net diff against `main` should only contain the revert of #13199. ### Checklist - [x] PR: The PR description is expressive enough and will help future contributors - [x] Code: Write code that humans can understand and Keep it simple - [x] Refactor: You have left the code cleaner than you found it (Boy Scout Rule) - [x] Upgrade: Impact of this change on upgrade flows was considered and addressed if required - [ ] Documentation: N/A - no user-facing change - [x] Self-review: I have reviewed my own code before requesting review from others ### Release note ```release-note NONE ``` --------- Co-authored-by: Claude Opus 4.6 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Before this PR:
Feishu issue notification cards did not @mention any specific user, so notifications could be easily missed.
After this PR:
The issue notification card now includes an
<at>element that @mentions the Feishu usercli_a92d6e7ba3f85cedin the card body, ensuring they receive a direct notification for every new GitHub issue.Why we need it and why it was done in this way
The Feishu user needs to be actively notified when new GitHub issues are created. By embedding the
<at id=cli_a92d6e7ba3f85ced></at>tag directly in the card's lark_md content, the user gets a native Feishu @mention notification without requiring changes to the workflow or CLI interface.The following tradeoffs were made:
The following alternatives were considered:
--mentionCLI option: More flexible but unnecessary complexity for a single user.Breaking changes
None.
Special notes for your reviewer
The TypeScript diagnostics shown for
feishu-notify.ts(missingprocess,Buffer, etc.) are pre-existing and unrelated to this change — the script runs vianpx tsxand is outside the project's tsconfig scope.Checklist
/gh-pr-review,gh pr diff, or GitHub UI) before requesting review from othersRelease note