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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -991,7 +991,7 @@ The following sets of tools are available:
991
991
2. get_diff - Get the diff of a pull request.
992
992
3. get_status - Get status of a head commit in a pull request. This reflects status of builds and checks.
993
993
4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.
994
-
5. get_review_comments - Get the review comments on a pull request. They are comments made on a portion of the unified diff during a pull request review. Use with pagination parameters to control the number of results returned.
994
+
5. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results.
995
995
6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.
996
996
7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.
997
997
(string, required)
@@ -1092,7 +1092,7 @@ The following sets of tools are available:
1092
1092
1093
1093
-**get_file_contents** - Get file or directory contents
1094
1094
-`owner`: Repository owner (username or organization) (string, required)
1095
-
-`path`: Path to file/directory (directories must end with a slash '/') (string, optional)
1095
+
-`path`: Path to file/directory (string, optional)
1096
1096
-`ref`: Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head` (string, optional)
1097
1097
-`repo`: Repository name (string, required)
1098
1098
-`sha`: Accepts optional commit SHA. If specified, it will be used instead of ref (string, optional)
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/pull_request_read.snap
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@
15
15
"properties": {
16
16
"method": {
17
17
"type": "string",
18
-
"description": "Action to specify what pull request data needs to be retrieved from GitHub. \nPossible options: \n 1. get - Get details of a specific pull request.\n 2. get_diff - Get the diff of a pull request.\n 3. get_status - Get status of a head commit in a pull request. This reflects status of builds and checks.\n 4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.\n 5. get_review_comments - Get the review comments on a pull request. They are comments made on a portion of the unified diff during a pull request review. Use with pagination parameters to control the number of results returned.\n 6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.\n 7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.\n",
18
+
"description": "Action to specify what pull request data needs to be retrieved from GitHub. \nPossible options: \n 1. get - Get details of a specific pull request.\n 2. get_diff - Get the diff of a pull request.\n 3. get_status - Get status of a head commit in a pull request. This reflects status of builds and checks.\n 4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.\n 5. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results.\n 6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.\n 7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.\n",
// PullRequestRead creates a tool to get details of a specific pull request.
24
-
funcPullRequestRead(getClientGetClientFn, cache*lockdown.RepoAccessCache, t translations.TranslationHelperFunc, flagsFeatureFlags) (mcp.Tool, mcp.ToolHandlerFor[map[string]any, any]) {
24
+
funcPullRequestRead(getClientGetClientFn, getGQLClientGetGQLClientFn, cache*lockdown.RepoAccessCache, t translations.TranslationHelperFunc, flagsFeatureFlags) (mcp.Tool, mcp.ToolHandlerFor[map[string]any, any]) {
25
25
schema:=&jsonschema.Schema{
26
26
Type: "object",
27
27
Properties: map[string]*jsonschema.Schema{
@@ -33,7 +33,7 @@ Possible options:
33
33
2. get_diff - Get the diff of a pull request.
34
34
3. get_status - Get status of a head commit in a pull request. This reflects status of builds and checks.
35
35
4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.
36
-
5. get_review_comments - Get the review comments on a pull request. They are comments made on a portion of the unified diff during a pull request review. Use with pagination parameters to control the number of results returned.
36
+
5. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results.
37
37
6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.
38
38
7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.
0 commit comments