Fix auto-triage comment preparation and quota misuse - #4693
Open
priyankatiwari08 wants to merge 1 commit into
Open
priyankatiwari08 wants to merge 1 commit into
priyankatiwari08 wants to merge 1 commit into
Conversation
Allow jq for the documented JSON payload path and prohibit diagnostic comment writes that consume the single-comment quota. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
priyankatiwari08
requested review from
a team
and
a balanced review from Copilot
September 15, 2026 16:14
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The documented JSON-mode submission command does not provide the generated payload on stdin.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Fixes issue auto-triage output preparation and prevents placeholder comments from consuming the comment quota.
Changes:
- Allows
jqfor JSON payload construction. - Adds safe-output usage guardrails.
- Regenerates the pinned workflow lock file.
File summaries
| File | Description |
|---|---|
.github/workflows/issue-triage.md |
Adds jq and safe-output instructions. |
.github/workflows/issue-triage.lock.yml |
Regenerates workflow permissions and metadata. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Balanced
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| the allowance. The target argument is `item_number`, not `issue_number`. | ||
| For a multi-line summary saved to a temporary file, use the allowed `jq -Rs` | ||
| command to construct the JSON payload with `item_number` and `body`, then | ||
| submit it once through `safeoutputs add_comment .`. |
cheenamalhotra
approved these changes
Sep 15, 2026
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
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.
Description
Fix the failure in https://github.com/dotnet/SqlClient/actions/runs/34991102115: generated instructions recommended
jq, but the workflow denied it. During debugging the agent postedtest comment, exhaustingadd_comment's one-comment quota before submitting its real summary.jqfor JSON payload preparation.--help.item_numbertargeting and stop repeated denied-command retries.Preserves comment limits, label restrictions, triggers, and GitHub permissions. No runtime/API changes.
Issues
Fixes #4692. Affected triage target: #4691.
Testing
gh aw compilesucceeded with zero warnings; a second compile left the lock file unchanged. Generated permissions includeshell(jq).git diff --checkpassed. No application tests added because only workflow configuration and instructions change. Fixed live execution is pending merge.After merge, a maintainer should post
/triageon #4691 and verify one complete summary and noreport_incomplete. The erroneous test comment has not been deleted.Guidelines