Migrate PR #1515 changes to modelcontextprotocol/go-sdk

Resolves merge conflicts by migrating the review threads refactoring
from mark3labs/mcp-go to modelcontextprotocol/go-sdk:

- PullRequestRead now uses getGQLClient for get_review_comments
- GetPullRequestReviewComments uses GraphQL to fetch review threads
- Added GraphQL types for review threads query
- Updated tests and toolsnaps for new SDK patterns

Co-authored-by: tonytrg <[email protected]>

Author: Copilot

.github/copilot-instructions.md

@@ -9,7 +9,7 @@ This is the **GitHub MCP Server**, a Model Context Protocol (MCP) server that co
 - **Type:** MCP server application with CLI interface
 - **Primary Package:** github-mcp-server (stdio MCP server - **this is the main focus**)
 - **Secondary Package:** mcpcurl (testing utility - don't break it, but not the priority)
-- **Framework:** Uses mark3labs/mcp-go for MCP protocol, google/go-github for GitHub API
+- **Framework:** Uses modelcontextprotocol/go-sdk for MCP protocol, google/go-github for GitHub API
 - **Size:** ~60MB repository, 70 Go files
 - **Library Usage:** This repository is also used as a library by the remote server. Functions that could be called by other repositories should be exported (capitalized), even if not required internally. Preserve existing export patterns.
 

.github/prompts/bug-report-review.prompt.yml

@@ -0,0 +1,32 @@
+messages:
+  - role: system
+    content: |
+      You are a triage assistant for the GitHub MCP Server repository. This is a Model Context Protocol (MCP) server that connects AI tools to GitHub's platform, enabling AI agents to manage repositories, issues, pull requests, workflows, and more.
+
+      Your job is to analyze bug reports and assess their completeness.
+
+      Analyze the issue for these key elements:
+      1. Clear description of the problem
+      2. Affected version (from running `docker run -i --rm ghcr.io/github/github-mcp-server ./github-mcp-server --version`)
+      3. Steps to reproduce the behavior
+      4. Expected vs actual behavior
+      5. Relevant logs (if applicable)
+
+      Provide ONE of these assessments:
+
+      ### AI Assessment: Ready for Review
+      Use when the bug report has most required information and can be triaged by a maintainer.
+
+      ### AI Assessment: Missing Details
+      Use when critical information is missing (no reproduction steps, no version info, unclear problem description).
+
+      ### AI Assessment: Unsure
+      Use when you cannot determine the completeness of the report.
+
+      After your assessment header, provide a brief explanation of your rating.
+      If details are missing, note which specific sections need more information.
+  - role: user
+    content: "{{input}}"
+model: openai/gpt-4o-mini
+modelParameters:
+  max_tokens: 500

.github/prompts/default-issue-review.prompt.yml

@@ -0,0 +1,31 @@
+messages:
+  - role: system
+    content: |
+      You are a triage assistant for the GitHub MCP Server repository. This is a Model Context Protocol (MCP) server that connects AI tools to GitHub's platform, enabling AI agents to manage repositories, issues, pull requests, workflows, and more.
+
+      Your job is to analyze new issues and help categorize them.
+
+      Analyze the issue to determine:
+      1. Is this a bug report, feature request, question, or something else?
+      2. Is the issue clear and well-described?
+      3. Does it contain enough information for maintainers to act on?
+
+      Provide ONE of these assessments:
+
+      ### AI Assessment: Ready for Review
+      Use when the issue is clear, well-described, and contains enough context for maintainers to understand and act on it.
+
+      ### AI Assessment: Missing Details
+      Use when the issue is unclear, lacks context, or needs more information to be actionable.
+
+      ### AI Assessment: Unsure
+      Use when you cannot determine the nature or completeness of the issue.
+
+      After your assessment header, provide a brief explanation including:
+      - What type of issue this appears to be (bug, feature request, question, etc.)
+      - What additional information might be helpful if any
+  - role: user
+    content: "{{input}}"
+model: openai/gpt-4o-mini
+modelParameters:
+  max_tokens: 500

.github/workflows/ai-issue-assessment.yml

@@ -0,0 +1,30 @@
+name: AI Issue Assessment
+
+on:
+  issues:
+    types: [opened, labeled]
+
+jobs:
+  ai-issue-assessment:
+    if: >
+      (github.event.action == 'opened' && github.event.issue.labels[0] == null) ||
+      (github.event.action == 'labeled' && github.event.label.name == 'bug')
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      models: read
+      contents: read
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Run AI assessment
+        uses: github/ai-assessment-comment-labeler@e3bedc38cfffa9179fe4cee8f7ecc93bffb3fee7 # v1.0.1
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          ai_review_label: 'bug, enhancement'
+          issue_number: ${{ github.event.issue.number }}
+          issue_body: ${{ github.event.issue.body }}
+          prompts_directory: '.github/prompts'
+          labels_to_prompts_mapping: 'bug,bug-report-review.prompt.yml|default,default-issue-review.prompt.yml'

.github/workflows/code-scanning.yml

@@ -35,7 +35,7 @@ jobs:
             runner: '["ubuntu-22.04"]'
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Initialize CodeQL
         uses: github/codeql-action/init@v4

.github/workflows/docker-publish.yml

@@ -40,7 +40,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       # Install the cosign tool except on PR
       # https://github.com/sigstore/cosign-installer

.github/workflows/docs-check.yml

@@ -14,7 +14,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Checkout code
-      uses: actions/checkout@v5
+      uses: actions/checkout@v6
 
     - name: Set up Go
       uses: actions/setup-go@v6

.github/workflows/go.yml

@@ -15,7 +15,7 @@ jobs:
 
     steps:
       - name: Check out code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Set up Go
         uses: actions/setup-go@v6

.github/workflows/goreleaser.yml

@@ -14,7 +14,7 @@ jobs:
 
     steps:
       - name: Check out code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Set up Go
         uses: actions/setup-go@v6

.github/workflows/license-check.yml

@@ -11,7 +11,7 @@ jobs:
 
     steps:
       - name: Check out code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v6
 
       - name: Set up Go
         uses: actions/setup-go@v6