nhcarrigan/hikari
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 2 Pull Requests 3 Actions Releases Activity

fix: correct announcement API endpoint and add optional content fields #20

Merged
naomi merged 4 commits from fix/announce into main 2026-03-23 15:59:42 -07:00
Conversation 0 Commits 4 Files Changed 4
+62 -17
hikari commented 2026-03-23 15:06:44 -07:00
Owner
Copy Link
Copy Source

Summary

  • Fixes the announcement API URL from /announcement to /api/announcement
  • Adds three optional additional content text inputs (Parts 2–4) to the announcement modal
  • The bot concatenates all non-empty content fields with double newlines before forwarding to the API
  • Only the first content field and the category selector remain required

Test Plan

  • Run /announcement and verify the modal opens with four content fields and a category selector
  • Submit with only the first content field filled — verify it sends correctly
  • Submit with multiple content fields filled — verify they are concatenated in the API request
  • Verify the API no longer returns HTTP 405
## Summary - Fixes the announcement API URL from `/announcement` to `/api/announcement` - Adds three optional additional content text inputs (Parts 2–4) to the announcement modal - The bot concatenates all non-empty content fields with double newlines before forwarding to the API - Only the first content field and the category selector remain required ## Test Plan - [ ] Run `/announcement` and verify the modal opens with four content fields and a category selector - [ ] Submit with only the first content field filled — verify it sends correctly - [ ] Submit with multiple content fields filled — verify they are concatenated in the API request - [ ] Verify the API no longer returns HTTP 405
hikari added 2 commits 2026-03-23 15:06:44 -07:00
fix: correct announcement API endpoint URL 0db0d220cc
feat: add three optional content fields to announcement modal
Node.js CI / CI (pull_request) Successful in 1m41s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 2m0s
Details
1c4bc9ca03
hikari added 1 commit 2026-03-23 15:08:47 -07:00
refactor: replace entitledUsers owner gate with naomiId
Node.js CI / CI (pull_request) Failing after 1m5s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m48s
Details
b5d29025b3
hikari added 1 commit 2026-03-23 15:25:15 -07:00
chore: commit naomiId entitlement config
Node.js CI / CI (pull_request) Successful in 43s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m6s
Details
ee796b6e57
naomi merged commit 39b22c9514 into main 2026-03-23 15:59:42 -07:00
naomi deleted branch fix/announce 2026-03-23 15:59:42 -07:00
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari#20
Delete Branch "fix/announce"

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?