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
+30-30Lines changed: 30 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -621,7 +621,7 @@ The following sets of tools are available:
621
621
-`inputs`: Inputs the workflow accepts. Only used for 'run_workflow' method. (object, optional)
622
622
-`method`: The method to execute (string, required)
623
623
-`owner`: Repository owner (string, required)
624
-
-`ref`: The git reference for the workflow. The reference can be a branch or tag name. Required for 'run_workflow' method. (string, optional)
624
+
-`ref`: Branch or tag name to run the workflow on. Required for 'run_workflow' method. (string, optional)
625
625
-`repo`: Repository name (string, required)
626
626
-`run_id`: The ID of the workflow run. Required for all methods except 'run_workflow'. (number, optional)
627
627
-`workflow_id`: The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for 'run_workflow' method. (string, optional)
@@ -655,7 +655,7 @@ The following sets of tools are available:
655
655
-`owner`: The owner of the repository. (string, required)
656
656
-`page`: Page number for pagination (min 1) (number, optional)
657
657
-`perPage`: Results per page for pagination (min 1, max 100) (number, optional)
658
-
-`ref`: The Git reference for the results you want to list. (string, optional)
658
+
-`ref`: Git ref to filter by, e.g. refs/heads/main or refs/pull/123/merge. (string, optional)
659
659
-`repo`: The name of the repository. (string, required)
660
660
-`severity`: Filter code scanning alerts by severity (string, optional)
661
661
-`state`: Filter code scanning alerts by state. Defaults to open (string, optional)
@@ -689,7 +689,7 @@ The following sets of tools are available:
689
689
690
690
-**assign_copilot_to_issue** - Assign Copilot to issue
691
691
-**Required OAuth Scopes**: `repo`
692
-
-`base_ref`: Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch (string, optional)
692
+
-`base_ref`: Branch or ref the agent starts from; defaults to the repository default branch (string, optional)
693
693
-`custom_instructions`: Optional custom instructions to guide the agent beyond the issue body. Use this to provide additional context, constraints, or guidance that is not captured in the issue description (string, optional)
694
694
-`issue_number`: Issue number (number, required)
695
695
-`owner`: Repository owner (string, required)
@@ -732,7 +732,7 @@ The following sets of tools are available:
-`body`: Comment content (required for 'add', 'reply', and 'update' methods) (string, optional)
735
+
-`body`: Comment content. Markdown supported. Required for 'add', 'reply', and 'update' methods. (string, optional)
736
736
-`commentNodeID`: The Node ID of the discussion comment (required for 'reply', 'update', 'delete', 'mark_answer', and 'unmark_answer' methods). For 'reply', this is the top-level comment to reply to; GitHub Discussions only support one level of nesting. (string, optional)
737
737
-`discussionNumber`: Discussion number (required for 'add' and 'reply' methods) (number, optional)
738
738
-`method`: Write operation to perform on a discussion comment.
@@ -785,7 +785,7 @@ The following sets of tools are available:
785
785
786
786
-**create_gist** - Create Gist
787
787
-**Required OAuth Scopes**: `gist`
788
-
-`content`: Content for simple single-file gist creation (string, required)
788
+
-`content`: Raw content for the single gist file (string, required)
789
789
-`description`: Description of the gist (string, optional)
790
790
-`filename`: Filename for simple single-file gist creation (string, required)
791
791
-`public`: Whether the gist is public (boolean, optional)
@@ -801,7 +801,7 @@ The following sets of tools are available:
801
801
802
802
-**update_gist** - Update Gist
803
803
-**Required OAuth Scopes**: `gist`
804
-
-`content`: Content for the file (string, required)
804
+
-`content`: Raw content for the gist file (string, required)
805
805
-`description`: Updated description of the gist (string, optional)
806
806
-`filename`: Filename to update or create (string, required)
807
807
-`gist_id`: ID of the gist to update (string, required)
@@ -828,7 +828,7 @@ The following sets of tools are available:
-`line`: The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range (number, optional)
1067
1067
-`owner`: Repository owner (string, required)
1068
1068
-`path`: The relative path to the file that necessitates a comment (string, required)
@@ -1075,28 +1075,28 @@ The following sets of tools are available:
1075
1075
1076
1076
-**add_reply_to_pull_request_comment** - Add reply to pull request comment
-`query`: Search query using GitHub pull request search syntax. Qualifiers such as is:pr and repo:owner/repo are applied automatically when appropriate; examples: "review-requested:@me", "author:octocat updated:>=2024-01-01". (string, required)
1154
1154
-`repo`: Optional repository name. If provided with owner, only pull requests for this repository are listed. (string, optional)
1155
1155
-`sort`: Sort field by number of matches of categories, defaults to best match (string, optional)
1156
1156
1157
1157
-**update_pull_request** - Edit pull request
1158
1158
-**Required OAuth Scopes**: `repo`
1159
-
-`base`: New base branch name (string, optional)
1159
+
-`base`: New base branch name, e.g. main. (string, optional)
1160
1160
-`body`: New description (string, optional)
1161
1161
-`draft`: Mark pull request as draft (true) or ready for review (false) (boolean, optional)
-`duplicate_of`: Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'. (number, optional)
81
81
-`issue_fields`: Issue field values to set or clear. Each item requires 'field_name' and exactly one of 'value', 'field_option_name', or 'delete: true'. (object[], optional)
82
82
-`issue_number`: Issue number to update (number, optional)
0 commit comments