-
-
Notifications
You must be signed in to change notification settings - Fork 89
REST + CLI mirror for loopover_watch_issues #6746
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_watch_issues(src/mcp/server.ts:2199, viawatchIssuesatsrc/mcp/server.ts:3849-3869) manages watch/unwatch/list issue-watch subscriptions, self-scoped viarequireContributorAccess+requireWatchableRepo. No REST route exists for this, and no CLI mirror exists.Requirements
GET/POST/DELETE /v1/contributors/:login/watchesinsrc/api/routes.tsreusing the same repository functions andrequireContributorAccess/canWatchRepogates.loopover-mcp watch <owner/repo> [--labels a,b]/unwatch/list).Deliverables
GET/POST/DELETE /v1/contributors/:login/watchesroutesTest 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
Issue-watch subscriptions are manageable over REST/CLI, not just MCP.
Links & Resources
Precedent: the contributor-scoped route family cited above, plus
requireWatchableRepoatsrc/mcp/server.ts:2966-2970for the access check to reuse verbatim.