Repository navigation
Expose tools to read and list repository issues #32
Description
Problem
Agents need to read a GitHub issue by number and list repository issues through Paca's tools. The current released GitHub plugin (v0.4.1) does not expose these operations. On the current default branch, the GitHub provider implements GetIssue, but the Git provider SPI has no ListIssues operation; MCP tools now live in Paca core rather than the plugin.
Expected behavior
- Retrieve an issue by number and list issues for a linked repository using the configured GitHub connection.
- Preserve project/repository authorization and return platform-authored text as untrusted data.
- Make issue listing paginated, distinguish issues from pull requests, and propagate provider errors.
- Cover the provider, API and MCP paths with tests.
The default-branch implementation requires coordinated changes to the Git provider SDK and Paca core as well as this provider. The core tool for a single issue is currently named issue_get.
Reacted by Hải Huỳnh
Reacted by Hải Huỳnh
Reacted by Hải Huỳnh
Activity
kayahk commentedon Nov 2, 2026
Context
The work spans three repositories because the GitHub plugin is now a provider behind Paca's core-owned Git tools.
The provider implementation is being prepared against the SDK change; it cannot be released until the SDK change is available. On the currently released plugin and core, neither requested issue tool is available.
kayahk commentedon Nov 2, 2026
GitHub provider draft: #33. It depends on the SDK and core drafts linked above; the temporary fork SDK pin must be replaced with an upstream release before merge.
pikann commentedon Nov 3, 2026
Done by #33 and #35. Closing this issue