Repository navigation
Conversation
2 tasks
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Diagnose stalled code scanning fixer attempts
Diagnose and release stalled code-scanning fixer attempts
Nov 9, 2026
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| started_at: (if $started == null then null else $record.started_at end), | ||
| timestamp_invalid: ($started == null) | ||
| timestamp_invalid: ($started == null), | ||
| last_successful_step: ($record.last_successful_step // "alert_selected"), |
This branch has not been deployed
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.
Stalled fixer attempts lacked a clear diagnostic and could remain unavailable for retry. The workflow now records the last completed milestone, reports the stale-checkpoint reason, and releases the alert after the diagnostic is accepted.
last_successful_stepafter each completed milestone.stalled_reportedafter the issue intent is accepted; the alert becomes eligible for selection on the next run.Example checkpoint:
{"alert_number":42,"outcome":"in_progress","started_at":"2026-11-06T21:00:00Z","last_successful_step":"vulnerability_analyzed"}