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.
Fix add_labels silently applying no labels #50637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix add_labels silently applying no labels #50637
Changes from all commits
83128b6b635537a1c0288File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnosing-bugs] Redundant
issues.getcall:fetchIssueState(line 258) already callsgithub.rest.issues.getunconditionally, then the intent path calls it again here to getnode_idandlabels. This doubles the REST cost and creates two separate failure points for every intent-label operation.💡 Suggested fix
Call
issues.getonce above theif (useIssueIntentPath)block and use the result for bothbeforeStateextraction and the intent path:This removes the extra round-trip and makes the failure surface smaller.
@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Redundant
issues.getcall — double-fetch on the intent path.fetchIssueState(line 258) already callsgithub.rest.issues.getinternally to capture the before-state. The intent path then makes a secondissues.getcall (here) solely to retrievenode_idand existing labels.This doubles the GitHub API calls on every intent-metadata label add. Either expose the raw issue data from
fetchIssueState, or callissues.getonce before thefetchIssueStatecall and derivebeforeStatefrom that data:@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnosing-bugs] Hard-coded
labels(first: 100)cap in the GraphQL response could silently truncate theafterLabelslist for issues with more than 100 labels, causingattachExecutionStateto report an incorrect post-operation label set.💡 Suggested fix
Use pagination or, at minimum, add a warning when the response indicates truncation:
Alternatively, bump the fragment to
first: 250(the GitHub API maximum) and add the guard.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.