You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or problem you'd like to solve
The current implementation of repository listing functionality in the GitHub MCP server doesn't properly handle forked repositories. When users try to list their repos or other repos they expect to see both their original repositories and their forks, but the current implementation doesn't provide this capability.
Current limitations:
Users cannot see their forked repositories in search results
Users cannot get a complete list of their repositories including forks
Users cannot filter repositories by fork status
Proposed solution
We have two potential approaches to solve this issue:
Enhance Search Repositories:
Modify the existing search_repositories function to add fork-specific parameters
Include fork status in search results
Support filtering by fork status
Create New Tool for Fork Management:
Create a new dedicated tool that lists user's forks specifically
Provide fork-specific operations
Integrate with existing repository listing functionality
Questions for community input:
Which approach would be more beneficial for users, creating an independent tool for listing forks or integrating with search_repositories?
Are there specific GitHub API endpoints I should consider or would help in this implementation?
I would like to create a PR to implement the chosen solution after gathering community feedback on the preferred approach and any additional requirements or considerations.
The text was updated successfully, but these errors were encountered:
Describe the feature or problem you'd like to solve
The current implementation of repository listing functionality in the GitHub MCP server doesn't properly handle forked repositories. When users try to list their repos or other repos they expect to see both their original repositories and their forks, but the current implementation doesn't provide this capability.
Current limitations:
Proposed solution
We have two potential approaches to solve this issue:
Enhance Search Repositories:
search_repositories
function to add fork-specific parametersCreate New Tool for Fork Management:
Questions for community input:
search_repositories
?I would like to create a PR to implement the chosen solution after gathering community feedback on the preferred approach and any additional requirements or considerations.
The text was updated successfully, but these errors were encountered: