nhcarrigan/amari
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 2 Pull Requests 6 Actions Releases 1 Activity

Add owner-only message context menu to forward messages to DMs #11

New Issue
Closed
opened 2026-02-07 20:51:19 -08:00 by hikari · 1 comment
hikari commented 2026-02-07 20:51:19 -08:00
Owner
Copy Link
Copy Source

Description

Add a message context menu command that allows the bot owner (Naomi) to forward any message to her DMs as if it matched the ping/name trigger.

Requirements

  • Context menu command: Right-click on any message → "Forward to Naomi"
  • Owner-only: Only Naomi (bot owner) should be able to use this command
  • Behaviour: When used, the message should be sent to Naomi's DMs using the same logic as the ping/name trigger
  • Use case: Allows Naomi to easily forward interesting messages to herself without having to ping Amari or use her name

Implementation Notes

  • Check that the command user is the bot owner before processing
  • Reuse the existing ping/name trigger logic to format and send the message
  • Should work on any message in any server where Amari is present
  • Consider adding proper error handling if Naomi's DMs are closed

Acceptance Criteria

  • Message context menu command is registered
  • Command only executes for the bot owner (Naomi)
  • Message is forwarded to Naomi's DMs using the ping/name trigger format
  • Command fails gracefully if DMs are closed or message cannot be sent
  • Other users get an ephemeral error if they try to use the command

✨ This issue was created with help from Hikari~ 🌸

## Description Add a message context menu command that allows the bot owner (Naomi) to forward any message to her DMs as if it matched the ping/name trigger. ## Requirements - **Context menu command**: Right-click on any message → "Forward to Naomi" - **Owner-only**: Only Naomi (bot owner) should be able to use this command - **Behaviour**: When used, the message should be sent to Naomi's DMs using the same logic as the ping/name trigger - **Use case**: Allows Naomi to easily forward interesting messages to herself without having to ping Amari or use her name ## Implementation Notes - Check that the command user is the bot owner before processing - Reuse the existing ping/name trigger logic to format and send the message - Should work on any message in any server where Amari is present - Consider adding proper error handling if Naomi's DMs are closed ## Acceptance Criteria - [ ] Message context menu command is registered - [ ] Command only executes for the bot owner (Naomi) - [ ] Message is forwarded to Naomi's DMs using the ping/name trigger format - [ ] Command fails gracefully if DMs are closed or message cannot be sent - [ ] Other users get an ephemeral error if they try to use the command ✨ This issue was created with help from Hikari~ 🌸
teklu commented 2026-02-07 21:45:45 -08:00
Member
Copy Link
Copy Source

i would love to work on this one, can i assign my self

i would love to work on this one, can i assign my self
teklu was assigned by naomi 2026-02-07 21:48:08 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees teklu
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/amari#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?