Skip to content

Unable to look up PR or commit of requested change. #281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jcmanzo opened this issue Apr 15, 2025 · 1 comment
Open

Unable to look up PR or commit of requested change. #281

jcmanzo opened this issue Apr 15, 2025 · 1 comment
Labels
enhancement New feature or request tool-improvement

Comments

@jcmanzo
Copy link

jcmanzo commented Apr 15, 2025

Describe the bug

I have a private repo and MCP is able to tell me information about open PRs. However, when I want to find the specific PR or commit where a particular code change was introduced, such as a metric app.my_metric.health, the agent fails to find any PRs or commits. Here's my prompt:

Link me to the PR in foo/bar where the "app.my_metric.health" metric was added

The agent stumbles on this prompt. It first tries to find the local file where the metric is located which it finds correctly but then it runs search_code on the remote repo, then search_issues and then search_code again showing me the same local file location. It repeats the previous 3 external search calls again before finally giving up with:

Unfortunately, I wasn't able to identify the specific PR where this metric was introduced using the available tools. 

Affected version

Please run docker run -i --rm ghcr.io/github/github-mcp-server ./github-mcp-server --version and paste the output below

server version v0.1.1 (7ab5d968e065f13a660cd123c2c5d0be6d8b6dbd) 2025-04-07T16:05:10Z

I've tried both latest and main. In main, the agent searches the git log locally for a commit containing the code change.

Steps to reproduce the behavior

  1. Install the MCP server and give it a PAT with access to read repos
  2. Confirm that token is valid since agent is able to find info about open PRs
  3. Ask agent to look for a specific metric in the code (or any code really)
  4. Observe agent goes into loop, first checking for local file and then issuing external calls to GitHub
  5. Agent eventually gives up and is unable to find requested information.

Expected vs actual behavior

Agent should be able to list the PR or commit in which a code change was added. Ideally it should be able to provide a link to the commit/PR.

Logs

Paste any available logs. Redact if needed.

@jcmanzo jcmanzo added the bug Something isn't working label Apr 15, 2025
@SamMorrowDrums
Copy link
Collaborator

I think this is a really cool advanced use-case and I'd love to get to a point where this just works OOTB

@SamMorrowDrums SamMorrowDrums added enhancement New feature or request tool-improvement and removed bug Something isn't working labels Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tool-improvement
Projects
None yet
Development

No branches or pull requests

2 participants