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

feat: add owner-only context menu to forward messages to DMs #13

Closed
teklu wants to merge 0 commits from feature/owner-forward-message into feat/commands
pull from: feature/owner-forward-message
merge into: nhcarrigan:feat/commands
Conversation 1 Commits - Files Changed -
teklu commented 2026-02-16 08:27:34 -08:00
Member
Copy Link
Copy Source

Explanation

This PR is necessary because Naomi needs this feature on her Amari bot to forward messages to her DMs!

closes #11

Issue

No response

Attestations

Dependencies

  • I have pinned the dependencies to a specific patch version.

Style

  • I have run the linter and resolved any errors.
  • My pull request uses an appropriate title, matching the conventional commit standards.
  • My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.

Tests

  • My contribution adds new code, and I have added tests to cover it.
  • My contribution modifies existing code, and I have updated the tests to reflect these changes.
  • All new and existing tests pass locally with my changes.
  • Code coverage remains at or above the configured threshold.

Documentation

No response

Versioning

Major - My pull request introduces a breaking change.

### Explanation This PR is necessary because Naomi needs this feature on her Amari bot to forward messages to her DMs! closes #11 ### Issue _No response_ ### Attestations - [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/) - [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/). - [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/). ### Dependencies - [ ] I have pinned the dependencies to a specific patch version. ### Style - [x] I have run the linter and resolved any errors. - [x] My pull request uses an appropriate title, matching the conventional commit standards. - [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request. ### Tests - [x] My contribution adds new code, and I have added tests to cover it. - [x] My contribution modifies existing code, and I have updated the tests to reflect these changes. - [x] All new and existing tests pass locally with my changes. - [x] Code coverage remains at or above the configured threshold. ### Documentation _No response_ ### Versioning Major - My pull request introduces a breaking change.
naomi changed target branch from main to feat/commands 2026-03-03 10:21:19 -08:00
naomi added 4 commits 2026-03-03 10:21:19 -08:00
feat: add owner-only message context menu to forward messages to DMs 0394d03361
fix: fix lint erorr
Node.js CI / CI (pull_request) Failing after 23s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 50s
Details
0a3c000add
fix: solve linter error
Node.js CI / CI (pull_request) Failing after 24s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 53s
Details
60fec0f2d8
fix: solve linter error
Node.js CI / CI (pull_request) Successful in 28s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 51s
Details
10c7d337a5
hikari commented 2026-03-03 11:01:22 -08:00
Owner
Copy Link
Copy Source

Hey there! Thank you so much for this contribution β€” we really appreciate you taking the time to add this feature! πŸŽ‰

Rather than merging directly through Gitea, we've manually pulled your changes into our feat/commands branch where we're building out the full commands suite. Your commits are fully preserved in the history there with complete credit to you β€” nothing was squashed or lost!

We're closing this PR since the changes are already in, but please don't let that discourage you β€” contributions like this are always welcome, and we'd love to see more from you! Feel free to open issues or PRs anytime. πŸ’•

✨ This comment was left with help from Hikari~ 🌸

Hey there! Thank you so much for this contribution β€” we really appreciate you taking the time to add this feature! πŸŽ‰ Rather than merging directly through Gitea, we've manually pulled your changes into our `feat/commands` branch where we're building out the full commands suite. Your commits are fully preserved in the history there with complete credit to you β€” nothing was squashed or lost! We're closing this PR since the changes are already in, but please don't let that discourage you β€” contributions like this are always welcome, and we'd love to see more from you! Feel free to open issues or PRs anytime. πŸ’• ✨ This comment was left with help from Hikari~ 🌸
hikari closed this pull request 2026-03-03 11:01:45 -08:00
Node.js CI / CI (pull_request) Successful in 28s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 51s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/amari#13
Delete Branch "feature/owner-forward-message"

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?