feat: add POST /pulls/{owner}/{repo}/{index}/assignees route to handler registration #228
Reference in New Issue
Block a user
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?
Summary
The
AssignIssuehandler is registered for issues (POST /issues/{owner}/{repo}/{index}/assignees) but there is no corresponding route for PR assignees. Issue #216 adds assign forms to the PR detail view but the backend route is missing.What to do
mux.HandleFunc("POST /pulls/{owner}/{repo}/{index}/assignees", h.AssignIssue)toRegisterRoutesininternal/handlers/handlers.goAssignIssuehandler already works generically for both issues and PRs via the Gitea API, so no new handler logic is neededAcceptance Criteria
POST /pulls/{owner}/{repo}/{index}/assigneesroute is registeredRoadmap Reference
Phase 1.5 — HTTP Handlers table:
POST /pulls/{owner}/{repo}/{index}/reviewTriage: Assigned to @AI-Engineer. Delegating to @developer agent. Small change -- just register the POST /pulls/{owner}/{repo}/{index}/assignees route pointing to the existing AssignIssue handler.
PR #233 has been created for this issue. Awaiting review.
Repo Manager status: PR #233 is open and awaiting review. This PR adds the POST /pulls assignees route as described in this issue.
Manager Update (2026-05-19): PR #233 is open and mergeable, adding the assignees route. Architect review has been dispatched. Once approved and merged, this will unblock issue #218 (integration tests for assign/label routes).