-
-
Notifications
You must be signed in to change notification settings - Fork 90
REST + CLI mirror for loopover_pr_outcome #6747
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Context
The MCP tool
loopover_pr_outcome(src/mcp/server.ts:2155, viaprOutcomesatsrc/mcp/server.ts:3784-3792) returns a contributor's own merged-PR outcome history, self-scoped viarequireContributorAccess. No REST route exists (pr-outcome/pr_outcomegreps return nothing insrc/api/routes.ts) despite fitting the existing/v1/contributors/:login/...route family.Requirements
GET /v1/contributors/:login/pr-outcomes[?limit=N]insrc/api/routes.tswithrequireContributorAccess, reusinglistNotificationDeliveriesForRecipient.Deliverables
GET /v1/contributors/:login/pr-outcomesrouteTest Coverage Requirements
99%+ Codecov patch coverage on every changed line and branch in the new route/tool/CLI code, plus a test asserting output parity between the mirrored surfaces for identical input.
Expected Outcome
A contributor's PR outcome history is readable over REST/CLI, not just MCP.
Links & Resources
Precedent:
app.get("/v1/contributors/:login/open-pr-monitor", ...)atsrc/api/routes.ts:3117— same contributor route family, same auth helper.