Require explicit noop signal in Code Scanning Fixer to prevent false failures on API errors #10783
+27
−6
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.
The Code Scanning Fixer workflow failed with
missing finish_reason for choice 0despite successfully finding no alerts to fix. This transient Copilot API error occurred after the agent completed its work, causing spurious failure tracking issues.Changes
nooptool when no alerts are foundnoop(message="...")callsnoopsignals persist even if CLI fails afterwardWhy this works
The safe output system captures
noopcalls independently of CLI completion. When the API fails mid-response, the previously recordednoopsignal indicates successful completion, preventing false failure reports.Before:
- If no unfixed high severity alerts remain, exit gracefully with message: "..."After:
The workflow now distinguishes between genuine failures (agent couldn't complete work) and transient API errors (agent completed work, CLI failed afterward).
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.