Add per-label is_suggestion and rationale to issue_write#2656
Draft
iulia-b wants to merge 1 commit into
Draft
Conversation
Extend the general issue_write tool so each label can be sent either as a plain name or as an object with optional rationale (<=280 chars) and is_suggestion. On update, labels with intent are sent in object form (mapping is_suggestion to suggest); the create path strips intent. Mirrors the granular update_issue_labels behavior.
alondahari
approved these changes
Jun 9, 2026
alondahari
left a comment
alondahari
left a comment
Member
There was a problem hiding this comment.
Looks good, just a comment about extensibility
Comment on lines
+1878
to
+1879
| Description: "If true, this label is sent to the API as a suggestion rather than an applied label. " + | ||
| "Whether the label is applied or recorded as a proposal is determined by the API. Only honored when updating an existing issue.", |
Member
There was a problem hiding this comment.
Suggested change
| Description: "If true, this label is sent to the API as a suggestion rather than an applied label. " + | |
| "Whether the label is applied or recorded as a proposal is determined by the API. Only honored when updating an existing issue.", | |
| Description: "If true, this label is sent to the API as a suggestion rather than an applied label. " |
Is this second line needed?
| // stripped), the object-form payload to send when any label carries intent, | ||
| // whether any label carried intent, whether the labels parameter was provided | ||
| // at all, and an error. | ||
| func parseIssueWriteLabels(args map[string]any) (names []string, payload []any, hasIntent bool, provided bool, err error) { |
Member
There was a problem hiding this comment.
Should we make this implementation more reusable by other mutations like issue fields or issue types? Thinking it might be easier for us to build on in the future.
boazreicher
reviewed
Jun 9, 2026
| }, | ||
| "rationale": { | ||
| Type: "string", | ||
| Description: "One concise sentence explaining what specifically about the issue led you to choose this label. " + |
Contributor
There was a problem hiding this comment.
Since the limit is 280, why do we want to say that it's limited to one sentance?
Contributor
|
@iulia-b what about confidence arguments? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extend the general issue_write tool so each label can be sent either as a plain name or as an object with optional rationale (<=280 chars) and is_suggestion. On update, labels with intent are sent in object form (mapping is_suggestion to suggest); the create path strips intent. Mirrors the granular update_issue_labels behavior.
Summary
Why
Fixes https://github.com/github/plan-track-agentic-toolkit/issues/349
What changed
issue_writetool now supports labels suggestionsMCP impact
Prompts tested (tool changes only)
Security / limits
Tool renaming
deprecated_tool_aliases.goNote: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
./script/lint./script/testDocs