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
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -891,7 +891,7 @@ The following sets of tools are available:
891
891
-`issue_number`: The number of the issue (number, required)
892
892
-`method`: The read operation to perform on a single issue.
893
893
Options are:
894
-
1. get - Get details of a specific issue.
894
+
1. get - Get issue details. Also returns best-effort hierarchy flags (`has_parent`, `has_children`); `parent` and `sub_issues_summary` are optional relationship summaries.
895
895
2. get_comments - Get issue comments.
896
896
3. get_sub_issues - Get sub-issues (children) of the issue.
897
897
4. get_parent - Get the parent issue, if this issue is a sub-issue of another.
@@ -968,7 +968,8 @@ The following sets of tools are available:
968
968
- 'add' - add a sub-issue to a parent issue in a GitHub repository.
969
969
- 'remove' - remove a sub-issue from a parent issue in a GitHub repository.
970
970
- 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position.
971
-
(string, required)
971
+
Writes issue hierarchy. To move a sub-issue to a new parent, use `add` with `replace_parent=true`; there is no writable parent field.
972
+
(string, required)
972
973
-`owner`: Repository owner (string, required)
973
974
-`replace_parent`: When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional)
-`confidence`: How confident you are in this choice. Use 'HIGH' for clear signal or explicit user request, 'MEDIUM' for reasonable inference with some ambiguity, 'LOW' for best guess with limited signal. (string, optional)
182
+
-`duplicate_of`: The issue number of the canonical issue this issue duplicates. Only valid when state_reason is 'duplicate'. Required when is_suggestion is true and state_reason is 'duplicate'. The issue number is resolved to a database ID before being sent to the API. (number, optional)
183
+
-`is_suggestion`: If true, this state change is sent to the API as a suggestion (suggest:true) rather than an applied change. Whether the change is applied or recorded as a proposal is determined by the API. (boolean, optional)
181
184
-`issue_number`: The issue number to update (number, required)
182
185
-`owner`: Repository owner (username or organization) (string, required)
186
+
-`rationale`: One concise sentence explaining what specifically about the issue led you to choose this state. State the concrete signal (e.g. 'The reported crash is fixed in v2.1' → completed). (string, optional)
183
187
-`repo`: Repository name (string, required)
184
188
-`state`: The new state for the issue (string, required)
185
189
-`state_reason`: The reason for the state change (only for closed state) (string, optional)
0 commit comments