mcp-github-crunchtools 1.3.2__tar.gz → 1.5.0__tar.gz

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/CHANGELOG.md

@@ -6,6 +6,39 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+## [1.5.0] - 2026-10-20
+
+### Added
+
+- `merge_pull_request_tool` and `get_pull_request_checks_tool` work with a
+  fine-grained token. GitHub cannot grant one the Checks permission, so
+  check-runs answers 403; the tools then read the head commit's Actions jobs
+  (Actions: read), each of which is a check run with the same id and name.
+  Only Actions-reported checks are visible that way, so the merge gate
+  refuses a required check that names another app, or that accepts any app
+  and has no commit status. Both results carry `checks_source`.
+
+### Fixed
+
+- `get_pull_request_checks_tool` reads every page of check runs, not just the
+  first, up to the merge gate's page limit; past it the verdict says
+  `truncated` and is not `ready_to_merge`.
+
+## [1.4.0] - 2026-10-17
+
+### Added
+
+- `list_issue_comments_tool`: the comments on an issue or a pull request
+  conversation, oldest first, one page at a time, with id, author,
+  author_association, created_at, updated_at, body and html_url (#45).
+
+### Fixed
+
+- `list_pull_request_comments_tool` called on a plain issue returned GitHub's
+  403 "Resource not accessible by personal access token", which reads like a
+  token scope problem. It now says the number is an issue and points to
+  `list_issue_comments_tool` (#45).
+
 ## [1.3.2] - 2026-10-17
 
 ### Fixed

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/CLAUDE.md

@@ -1,6 +1,6 @@
 # Claude Code Instructions
 
-Secure MCP server for the GitHub REST API with 25 tools across issues, pull requests, Actions, releases, files, and search. Works with github.com and GitHub Enterprise Server.
+Secure MCP server for the GitHub REST API with 26 tools across issues, pull requests, Actions, releases, files, and search. Works with github.com and GitHub Enterprise Server.
 
 ## Quick Start
 
@@ -51,11 +51,11 @@ claude mcp add mcp-github-crunchtools \
 | `SSL_CERT_FILE` | No | — | Custom CA bundle for self-hosted instances |
 | `GITHUB_SSL_VERIFY` | No | `true` | Set `false` to disable SSL verification |
 
-## Available Tools (25)
+## Available Tools (26)
 
 | Category | Tools |
 |----------|-------|
-| Issues | `list_issues_tool`, `get_issue_tool`, `create_issue_tool`, `create_issue_comment_tool`, `update_issue_tool` |
+| Issues | `list_issues_tool`, `get_issue_tool`, `list_issue_comments_tool`, `create_issue_tool`, `create_issue_comment_tool`, `update_issue_tool` |
 | Pull Requests | `list_pull_requests_tool`, `get_pull_request_tool`, `get_pull_request_diff_tool`, `get_pull_request_checks_tool`, `list_pull_request_comments_tool`, `create_pull_request_tool`, `update_pull_request_tool`, `reply_to_review_comment_tool`, `merge_pull_request_tool` |
 | Files | `get_file_content_tool`, `list_repo_tree_tool` |
 | Search | `search_code_tool`, `search_issues_tool` |

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/Containerfile

@@ -27,7 +27,7 @@ FROM quay.io/hummingbird/python:latest
 
 # Labels for container metadata
 LABEL name="mcp-github-crunchtools" \
-      version="1.3.2" \
+      version="1.5.0" \
       summary="Secure MCP server for GitHub issues, pull requests, Actions, releases, files, and search" \
       description="A security-focused MCP server for GitHub built on Red Hat UBI" \
       maintainer="crunchtools.com" \

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mcp-github-crunchtools
-Version: 1.3.2
+Version: 1.5.0
 Summary: Secure MCP server for GitHub issues, pull requests, Actions, releases, files, and search
 Author: crunchtools.com
 License-Expression: AGPL-3.0-or-later
@@ -60,7 +60,7 @@ The container image is built on the [Hummingbird Python base image](https://quay
 
 ## Features
 
-25 tools. Tools marked *write* change something on GitHub; the others only
+26 tools. Tools marked *write* change something on GitHub; the others only
 read and publish `readOnlyHint`. The last column is the fine-grained token
 permission the tool needs (see [Token permissions](#token-permissions)).
 
@@ -70,6 +70,7 @@ permission the tool needs (see [Token permissions](#token-permissions)).
 |------|--------------|------------|
 | `list_issues_tool` | List issues for a repository (pull requests excluded) | Issues: read |
 | `get_issue_tool` | Get a single issue by number | Issues: read |
+| `list_issue_comments_tool` | Comments on an issue or a pull request conversation, oldest first | Issues: read, or Pull requests: read for a PR |
 | `create_issue_tool` | Open an issue (*write*) | Issues: write |
 | `create_issue_comment_tool` | Comment on an issue or pull request (*write*) | Issues: write, or Pull requests: write for a PR |
 | `update_issue_tool` | Edit, close or reopen an issue (*write*) | Issues: write |
@@ -81,12 +82,12 @@ permission the tool needs (see [Token permissions](#token-permissions)).
 | `list_pull_requests_tool` | List pull requests for a repository | Pull requests: read |
 | `get_pull_request_tool` | Get a single pull request by number | Pull requests: read |
 | `get_pull_request_diff_tool` | Get the unified diff for a pull request | Pull requests: read |
-| `get_pull_request_checks_tool` | CI verdict from check-runs and commit statuses; skipped is not failed | Pull requests: read, Commit statuses: read (and see the note under Token permissions) |
+| `get_pull_request_checks_tool` | CI verdict from check-runs and commit statuses; skipped is not failed | Pull requests: read, Commit statuses: read, Actions: read (and see the note under Token permissions) |
 | `list_pull_request_comments_tool` | Conversation comments, diff comments and reviews in one list, each tagged with its kind | Pull requests: read |
 | `create_pull_request_tool` | Open a pull request, optionally as a draft (*write*) | Pull requests: write |
 | `update_pull_request_tool` | Edit, close or reopen a pull request; does not merge (*write*) | Pull requests: write |
 | `reply_to_review_comment_tool` | Reply in the thread of a diff comment (*write*) | Pull requests: write |
-| `merge_pull_request_tool` | Merge, squash or rebase a pull request, only once the base branch's required checks are green on its head (see [The merge gate](#the-merge-gate)) (*write*) | Contents: write; Pull requests and Commit statuses: read |
+| `merge_pull_request_tool` | Merge, squash or rebase a pull request, only once the base branch's required checks are green on its head (see [The merge gate](#the-merge-gate)) (*write*) | Contents: write; Pull requests, Commit statuses and Actions: read |
 
 ### Actions (6 tools)
 
@@ -123,7 +124,10 @@ permission the tool needs (see [Token permissions](#token-permissions)).
 
 - `list_pull_request_comments_tool` reads each of its three kinds oldest
   first, up to 300 items per kind. `truncated` and `truncated_kinds` say when
-  newer items were left out.
+  newer items were left out. Called on a plain issue it says so; use
+  `list_issue_comments_tool` there.
+- `list_issue_comments_tool` returns one page (up to 100 comments); follow
+  `pagination.next_page` for more.
 - `get_workflow_run_tool` lists up to 300 jobs; `jobs_truncated` says when the
   run has more.
 - `get_failed_job_logs_tool` returns at most 1000 lines per job (200 by
@@ -218,16 +222,25 @@ For a fine-grained personal access token, the repository permissions are:
 |------------|--------------------|---------------------|
 | Metadata | every tool (GitHub grants it with any other permission) | — |
 | Contents | `get_file_content_tool`, `list_repo_tree_tool` | `merge_pull_request_tool`, `create_release_tool` |
-| Issues | `list_issues_tool`, `get_issue_tool` | `create_issue_tool`, `update_issue_tool`, `create_issue_comment_tool` |
+| Issues | `list_issues_tool`, `get_issue_tool`, `list_issue_comments_tool` | `create_issue_tool`, `update_issue_tool`, `create_issue_comment_tool` |
 | Pull requests | `merge_pull_request_tool`, `list_pull_requests_tool`, `get_pull_request_tool`, `get_pull_request_diff_tool`, `get_pull_request_checks_tool`, `list_pull_request_comments_tool` | `create_pull_request_tool`, `update_pull_request_tool`, `reply_to_review_comment_tool`, `create_issue_comment_tool` on a PR |
-| Actions | `list_workflow_runs_tool`, `get_workflow_run_tool`, `get_failed_job_logs_tool` | `trigger_workflow_tool`, `rerun_workflow_run_tool`, `rerun_failed_jobs_tool` |
+| Actions | `list_workflow_runs_tool`, `get_workflow_run_tool`, `get_failed_job_logs_tool`, `get_pull_request_checks_tool`, `merge_pull_request_tool` | `trigger_workflow_tool`, `rerun_workflow_run_tool`, `rerun_failed_jobs_tool` |
 | Commit statuses | `get_pull_request_checks_tool`, `merge_pull_request_tool` | — |
 
-`get_pull_request_checks_tool` and `merge_pull_request_tool` read check-runs, and GitHub's permission table
-for fine-grained tokens lists no permission for that endpoint. It is readable
-on public repositories; on a private repository use a classic token or a
-GitHub App token. The search tools likewise have no permission of their own:
-they return what the token can already read.
+`get_pull_request_checks_tool` and `merge_pull_request_tool` read check-runs,
+and GitHub's permission table for fine-grained tokens has no permission for
+that endpoint: a fine-grained token gets 403 on a private repository. Both
+tools then read the head commit's GitHub Actions jobs instead (Actions: read).
+Every Actions job is a check run with the same id and name, so the verdict
+and the merge gate are the same for checks GitHub Actions reports. Checks from
+any other app are not visible that way, so the merge gate refuses a required
+check that names another app, or that accepts any app and has no commit
+status, as missing. `checks_source` in each result says which was read, and
+the checks verdict then carries a `note` saying other apps' checks are not
+visible. Only the newest run of each workflow and event is read, and a commit
+with runs of more than 30 workflows is not judged.
+
+The search tools have no permission of their own: they return what the token can already read.
 
 Three things worth knowing before granting write:
 
@@ -262,7 +275,8 @@ merges it:
 4. requires, for every required check on the head commit, a completed check
    run of that name concluding `success`, `skipped` or `neutral` (the most
    recent run of the name decides), or a commit status of `success`. A rule
-   that names an app accepts only that app's check runs. A missing, pending
+   that names an app accepts only that app's check runs. A token that cannot
+   read check-runs is judged on the Actions jobs (see above). A missing, pending
    or failed check refuses the merge, and the error lists each one and why;
 5. reads the pull request again and refuses if its head or base changed
    meanwhile (GitHub's merge call pins the head but not the base), then

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/README.md

@@ -34,7 +34,7 @@ The container image is built on the [Hummingbird Python base image](https://quay
 
 ## Features
 
-25 tools. Tools marked *write* change something on GitHub; the others only
+26 tools. Tools marked *write* change something on GitHub; the others only
 read and publish `readOnlyHint`. The last column is the fine-grained token
 permission the tool needs (see [Token permissions](#token-permissions)).
 
@@ -44,6 +44,7 @@ permission the tool needs (see [Token permissions](#token-permissions)).
 |------|--------------|------------|
 | `list_issues_tool` | List issues for a repository (pull requests excluded) | Issues: read |
 | `get_issue_tool` | Get a single issue by number | Issues: read |
+| `list_issue_comments_tool` | Comments on an issue or a pull request conversation, oldest first | Issues: read, or Pull requests: read for a PR |
 | `create_issue_tool` | Open an issue (*write*) | Issues: write |
 | `create_issue_comment_tool` | Comment on an issue or pull request (*write*) | Issues: write, or Pull requests: write for a PR |
 | `update_issue_tool` | Edit, close or reopen an issue (*write*) | Issues: write |
@@ -55,12 +56,12 @@ permission the tool needs (see [Token permissions](#token-permissions)).
 | `list_pull_requests_tool` | List pull requests for a repository | Pull requests: read |
 | `get_pull_request_tool` | Get a single pull request by number | Pull requests: read |
 | `get_pull_request_diff_tool` | Get the unified diff for a pull request | Pull requests: read |
-| `get_pull_request_checks_tool` | CI verdict from check-runs and commit statuses; skipped is not failed | Pull requests: read, Commit statuses: read (and see the note under Token permissions) |
+| `get_pull_request_checks_tool` | CI verdict from check-runs and commit statuses; skipped is not failed | Pull requests: read, Commit statuses: read, Actions: read (and see the note under Token permissions) |
 | `list_pull_request_comments_tool` | Conversation comments, diff comments and reviews in one list, each tagged with its kind | Pull requests: read |
 | `create_pull_request_tool` | Open a pull request, optionally as a draft (*write*) | Pull requests: write |
 | `update_pull_request_tool` | Edit, close or reopen a pull request; does not merge (*write*) | Pull requests: write |
 | `reply_to_review_comment_tool` | Reply in the thread of a diff comment (*write*) | Pull requests: write |
-| `merge_pull_request_tool` | Merge, squash or rebase a pull request, only once the base branch's required checks are green on its head (see [The merge gate](#the-merge-gate)) (*write*) | Contents: write; Pull requests and Commit statuses: read |
+| `merge_pull_request_tool` | Merge, squash or rebase a pull request, only once the base branch's required checks are green on its head (see [The merge gate](#the-merge-gate)) (*write*) | Contents: write; Pull requests, Commit statuses and Actions: read |
 
 ### Actions (6 tools)
 
@@ -97,7 +98,10 @@ permission the tool needs (see [Token permissions](#token-permissions)).
 
 - `list_pull_request_comments_tool` reads each of its three kinds oldest
   first, up to 300 items per kind. `truncated` and `truncated_kinds` say when
-  newer items were left out.
+  newer items were left out. Called on a plain issue it says so; use
+  `list_issue_comments_tool` there.
+- `list_issue_comments_tool` returns one page (up to 100 comments); follow
+  `pagination.next_page` for more.
 - `get_workflow_run_tool` lists up to 300 jobs; `jobs_truncated` says when the
   run has more.
 - `get_failed_job_logs_tool` returns at most 1000 lines per job (200 by
@@ -192,16 +196,25 @@ For a fine-grained personal access token, the repository permissions are:
 |------------|--------------------|---------------------|
 | Metadata | every tool (GitHub grants it with any other permission) | — |
 | Contents | `get_file_content_tool`, `list_repo_tree_tool` | `merge_pull_request_tool`, `create_release_tool` |
-| Issues | `list_issues_tool`, `get_issue_tool` | `create_issue_tool`, `update_issue_tool`, `create_issue_comment_tool` |
+| Issues | `list_issues_tool`, `get_issue_tool`, `list_issue_comments_tool` | `create_issue_tool`, `update_issue_tool`, `create_issue_comment_tool` |
 | Pull requests | `merge_pull_request_tool`, `list_pull_requests_tool`, `get_pull_request_tool`, `get_pull_request_diff_tool`, `get_pull_request_checks_tool`, `list_pull_request_comments_tool` | `create_pull_request_tool`, `update_pull_request_tool`, `reply_to_review_comment_tool`, `create_issue_comment_tool` on a PR |
-| Actions | `list_workflow_runs_tool`, `get_workflow_run_tool`, `get_failed_job_logs_tool` | `trigger_workflow_tool`, `rerun_workflow_run_tool`, `rerun_failed_jobs_tool` |
+| Actions | `list_workflow_runs_tool`, `get_workflow_run_tool`, `get_failed_job_logs_tool`, `get_pull_request_checks_tool`, `merge_pull_request_tool` | `trigger_workflow_tool`, `rerun_workflow_run_tool`, `rerun_failed_jobs_tool` |
 | Commit statuses | `get_pull_request_checks_tool`, `merge_pull_request_tool` | — |
 
-`get_pull_request_checks_tool` and `merge_pull_request_tool` read check-runs, and GitHub's permission table
-for fine-grained tokens lists no permission for that endpoint. It is readable
-on public repositories; on a private repository use a classic token or a
-GitHub App token. The search tools likewise have no permission of their own:
-they return what the token can already read.
+`get_pull_request_checks_tool` and `merge_pull_request_tool` read check-runs,
+and GitHub's permission table for fine-grained tokens has no permission for
+that endpoint: a fine-grained token gets 403 on a private repository. Both
+tools then read the head commit's GitHub Actions jobs instead (Actions: read).
+Every Actions job is a check run with the same id and name, so the verdict
+and the merge gate are the same for checks GitHub Actions reports. Checks from
+any other app are not visible that way, so the merge gate refuses a required
+check that names another app, or that accepts any app and has no commit
+status, as missing. `checks_source` in each result says which was read, and
+the checks verdict then carries a `note` saying other apps' checks are not
+visible. Only the newest run of each workflow and event is read, and a commit
+with runs of more than 30 workflows is not judged.
+
+The search tools have no permission of their own: they return what the token can already read.
 
 Three things worth knowing before granting write:
 
@@ -236,7 +249,8 @@ merges it:
 4. requires, for every required check on the head commit, a completed check
    run of that name concluding `success`, `skipped` or `neutral` (the most
    recent run of the name decides), or a commit status of `success`. A rule
-   that names an app accepts only that app's check runs. A missing, pending
+   that names an app accepts only that app's check runs. A token that cannot
+   read check-runs is judged on the Actions jobs (see above). A missing, pending
    or failed check refuses the merge, and the error lists each one and why;
 5. reads the pull request again and refuses if its head or base changed
    meanwhile (GitHub's merge call pins the head but not the base), then

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mcp-github-crunchtools"
-version = "1.3.2"
+version = "1.5.0"
 description = "Secure MCP server for GitHub issues, pull requests, Actions, releases, files, and search"
 requires-python = ">=3.10"
 license = "AGPL-3.0-or-later"

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/crunchtools/mcp-github",
     "source": "github"
   },
-  "version": "1.3.0",
+  "version": "1.5.0",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "mcp-github-crunchtools",
-      "version": "1.3.0",
+      "version": "1.5.0",
       "transport": {
         "type": "stdio"
       }

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/src/mcp_github_crunchtools/__init__.py

@@ -29,7 +29,7 @@ import argparse
 
 from .server import mcp
 
-__version__ = "1.3.2"
+__version__ = "1.5.0"
 __all__ = ["main", "mcp"]
 
 

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/src/mcp_github_crunchtools/errors.py

@@ -44,6 +44,7 @@ class GitHubApiError(UserError):
 
     def __init__(self, code: int, message: str) -> None:
         super().__init__(f"GitHub API error {code}: {scrub_tokens(message)}")
+        self.status_code = code
 
 
 class NotFoundError(UserError):

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/src/mcp_github_crunchtools/server.py

@@ -21,6 +21,7 @@ from .tools import (
     get_pull_request_checks,
     get_pull_request_diff,
     get_workflow_run,
+    list_issue_comments,
     list_issues,
     list_pull_request_comments,
     list_pull_requests,
@@ -45,7 +46,7 @@ READ_ONLY = {"readOnlyHint": True}
 
 mcp = FastMCP(
     name="mcp-github",
-    version="1.3.2",
+    version="1.5.0",
     instructions=(
         "Secure MCP server for GitHub repositories: issues, pull requests "
         "(open, review discussion, diffs, CI checks, merge), Actions runs and "
@@ -106,6 +107,40 @@ async def get_issue_tool(
     return await get_issue(owner=owner, repo=repo, issue_number=issue_number)
 
 
+@mcp.tool(annotations=READ_ONLY)
+async def list_issue_comments_tool(
+    repo: str,
+    issue_number: Annotated[int, Field(ge=1)],
+    owner: str | None = None,
+    per_page: int = 30,
+    page: int = 1,
+) -> dict[str, Any]:
+    """List the comments on a GitHub issue or pull request conversation, oldest first.
+
+    Works for plain issues, which list_pull_request_comments_tool does not.
+    On a pull request it returns only the conversation comments; diff
+    comments and reviews come from list_pull_request_comments_tool.
+
+    Args:
+        repo: Repository name
+        issue_number: Issue or pull request number
+        owner: Repository owner (defaults to GITHUB_DEFAULT_ORG if unset)
+        per_page: Results per page, max 100 (default: 30)
+        page: Page number (default: 1)
+
+    Returns:
+        {"issue_number", "items", "pagination"?}; each item carries id,
+        author, author_association, created_at, updated_at, body, html_url
+    """
+    return await list_issue_comments(
+        owner=owner,
+        repo=repo,
+        issue_number=issue_number,
+        per_page=per_page,
+        page=page,
+    )
+
+
 @mcp.tool()
 async def create_issue_tool(
     repo: str,
@@ -270,7 +305,9 @@ async def get_pull_request_checks_tool(
     failing, pending, or skipped. SKIPPED checks are NOT failures. Use the
     returned ``ready_to_merge`` boolean as the signal for whether the PR is
     clear to merge (True only when nothing is failing or pending and the PR
-    is not known-unmergeable).
+    is not known-unmergeable). A token that cannot read check-runs (any
+    fine-grained token) gets the Actions jobs instead; ``checks_source`` says
+    which, and only Actions-reported checks are then visible.
 
     Args:
         repo: Repository name
@@ -372,7 +409,9 @@ async def merge_pull_request_tool(
     head; when branch protection cannot be read; and when the base branch
     requires no checks at all, unless ``allow_no_required_checks`` is True.
     Passing check runs conclude success, skipped or neutral. The merge is
-    pinned to the head SHA that was checked.
+    pinned to the head SHA that was checked. A token that cannot read
+    check-runs (any fine-grained token) is judged on the Actions jobs, and a
+    required check not reported by GitHub Actions is refused as missing.
 
     Args:
         repo: Repository name

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/src/mcp_github_crunchtools/tools/__init__.py

@@ -16,6 +16,7 @@ from .issues import (
     create_issue,
     create_issue_comment,
     get_issue,
+    list_issue_comments,
     list_issues,
     update_issue,
 )
@@ -45,6 +46,7 @@ __all__ = [
     "get_pull_request_checks",
     "get_pull_request_diff",
     "get_workflow_run",
+    "list_issue_comments",
     "list_issues",
     "list_pull_request_comments",
     "list_pull_requests",

{mcp_github_crunchtools-1.3.2 → mcp_github_crunchtools-1.5.0}/src/mcp_github_crunchtools/tools/issues.py

@@ -88,6 +88,62 @@ async def get_issue(
     return await client.get(f"/repos/{owner}/{repo}/issues/{issue_number}")
 
 
+async def list_issue_comments(
+    owner: str | None,
+    repo: str,
+    issue_number: int,
+    per_page: int = 30,
+    page: int = 1,
+) -> dict[str, Any]:
+    """List the comments on an issue or a pull request conversation, oldest first.
+
+    Diff comments and reviews on a pull request are not included; use
+    list_pull_request_comments for those.
+
+    Args:
+        owner: Repository owner (defaults to GITHUB_DEFAULT_ORG if unset)
+        repo: Repository name
+        issue_number: Issue or pull request number
+        per_page: Results per page (max 100)
+        page: Page number
+
+    Returns:
+        {"issue_number", "items", "pagination"?}; each item carries id,
+        author, author_association, created_at, updated_at, body, html_url
+    """
+    owner = resolve_owner(owner)
+    repo = validate_name(repo, "repo")
+    issue_number = validate_positive_int(issue_number, "issue_number")
+
+    client = get_client()
+    result = await client.get(
+        f"/repos/{owner}/{repo}/issues/{issue_number}/comments",
+        params={
+            "per_page": clamp_per_page(per_page),
+            "page": validate_positive_int(page, "page"),
+        },
+    )
+
+    response: dict[str, Any] = {
+        "issue_number": issue_number,
+        "items": [
+            {
+                "id": raw.get("id"),
+                "author": (raw.get("user") or {}).get("login"),
+                "author_association": raw.get("author_association"),
+                "created_at": raw.get("created_at"),
+                "updated_at": raw.get("updated_at"),
+                "body": raw.get("body") or "",
+                "html_url": raw.get("html_url"),
+            }
+            for raw in result.get("items", [])
+        ],
+    }
+    if "pagination" in result:
+        response["pagination"] = result["pagination"]
+    return response
+
+
 async def create_issue(
     owner: str | None,
     repo: str,
@@ -169,9 +225,7 @@ async def update_issue(
         json_data["state"] = state
     if state_reason is not None:
         if state_reason not in ("completed", "not_planned", "reopened"):
-            raise ValidationError(
-                "state_reason must be 'completed', 'not_planned', or 'reopened'"
-            )
+            raise ValidationError("state_reason must be 'completed', 'not_planned', or 'reopened'")
         json_data["state_reason"] = state_reason
     if title is not None:
         json_data["title"] = title