Repository navigation
[pr-sous-chef] PR Sous Chef run report #50715
Description
> ⚠️ **This is an automated status report. Do not assign this issue to a Copilot agent.**
Overview
Processed recent eligible non-draft PR candidates from the compact queue and nudged maintainable branches that were not blocked by active sous-chef cooldown rules. No formatter-generated changes were needed, and no review-thread cleanup actions were performed this run.
Critical Information
| Counter | Value |
|---|---|
| processed | 3 |
| skipped_checks_running | 0 |
| skipped_last_comment_from_sous_chef | 1 |
| skipped_cooldown | 0 |
| nudged | 2 |
| branch_update_attempts | 2 |
| formatter_pushes | 0 |
| merge_main_scheduled | 0 |
| resolved_review_threads | 0 |
| dismissed_reviews | 0 |
Nudged PRs
- Bump Claude, Copilot, Zizmor, and MCP Gateway defaults #50696 — Bump Claude, Copilot, Zizmor, and MCP Gateway defaults
- Add full-repo audit mode to pkg/linters/errormessage #50695 — Add full-repo audit mode to pkg/linters/errormessage
Recommendations
- Maintainers can inspect Add full-repo audit mode to pkg/linters/errormessage #50695 first because it still has a failed JS shard check.
- Deduplicate custom linter analyzer scaffolding #50700 was skipped because the latest comment was already a recent sous-chef nudge with
@copilot.
Generated by 👨🍳 PR Sous Chef · gpt54 · 12.3 AIC · ⌖ 9.76 AIC · ⊞ 8.3K · ◷
Comment /souschef to run again
- expires on Aug 8, 2026, 4:18 PM UTC-08:00
Activity
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed 3 eligible non-draft PRs from the compact candidate list and nudged all 3. No formatter pushes, review-thread resolutions, or stale-review dismissals were needed in this run.
Counters
Nudged PRs
max-ai-creditsto external detector AWF config #50721 — fix: propagatemax-ai-creditsto external detector AWF configgithub-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Automated PR triage processed the top four candidate PRs from the compact input and nudged the two with actionable unresolved feedback. No formatter changes were needed on the checked branches, and no PR had active pending checks within the 1-hour skip window.
Recommendations
Focus maintainer attention on PRs #50723 and #50717 after follow-up commits arrive. PRs #50721 and #50695 were skipped because a recent sous-chef/copilot interaction already exists within the cooldown rules.
Nudged PRs
Skipped PRs
max-ai-creditsto external detector AWF config #50721 — latest sous-chef +@copilotcomment / cooldown window@copilotfollow-up / cooldown windowgithub-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Nudged PRs
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed 1 eligible non-draft PR and nudged 1 PR for unresolved review follow-up. No formatter push was made because
make fmtfailed locally due to the available Go toolchain being older than the repo requirement.Critical Information
Nudged PRs
Recommendations
The PR should address the three unresolved review threads, let checks settle, and then run the pr-finisher skill.
Notes
copilot/avoid-mcp-stderr-artifact.make fmtfailed becausego.modrequires Go >= 1.26.5 while the environment provides Go 1.25.12 withGOTOOLCHAIN=local.gh pr checkswas unavailable here due to a GraphQL access error, so pending-check detection fell back to the commit status API, which reported the head SHA aspending.github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed eligible pull requests for a lightweight triage pass. No PRs were nudged in this run because the only candidate still has a pending status check started less than 1 hour ago.
Critical Information
Recommendations
Wait for the in-flight check on PR #50746 to complete before posting any sous-chef nudge.
Processed PR details
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Nudged PRs
Skipped PRs
@copilotfollow-upgithub-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed 1 eligible pull request candidate and nudged 1 PR for maintainer follow-up. No pending checks blocked action in this run.
Critical Information
Nudged PRs
Recommendations
Maintainer should inspect the remaining unresolved review threads and the stuck JavaScript test process referenced on the PR before merge.
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Nudged PRs
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Nudged PRs
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed 2 eligible non-draft PR candidates from the compact queue. No new nudges were posted because both PR head commits still show pending checks started recently enough to trigger the running-checks skip rule.
Critical information
Skipped PR details
2f097a86bd8909e5406c64bc3ceb2afa04c0f827pendinga5819d73074a071ebd8fc3eefb7d6ecdff902d24pendingRecommendations
Wait for the currently pending checks to finish before sending another sous-chef nudge. Once checks are no longer freshly running, PR #50776 is the next likely candidate because it still has unresolved review threads with follow-up replies.
Run metadata
/tmp/gh-aw/agent/pr-sous-chef-candidates-compact.jsongithub-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Nudged PRs
Skipped PRs
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Nudged PRs
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed recent PR candidates and posted 4 nudges, prioritizing a merge-conflict case and PRs with unresolved review feedback.
Nudged PRs
threat-detect concludeon the external path #50854 — threat-detection: delegate all conclude branches tothreat-detect concludeon the external pathRecommendations
Maintainers should review the newly posted nudges and the linked unresolved threads/check failures to decide which PRs need direct intervention versus routine copilot follow-up.
github-actions commentedon Aug 6, 2026
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Processed the top 4 candidate PRs by recency. No formatter changes were produced locally, branch refresh was requested on all 4 via PR update, and each PR received one combined sous-chef nudge.
Critical Information
Nudged PRs
threat-detect concludeon the external path #50854 — threat-detection: delegate all conclude branches tothreat-detect concludeon the external pathRecommendations
Maintainers can inspect these four PRs first; each was asked to resolve remaining review feedback, refresh if needed, and run the pr-finisher skill.
github-actions commentedon Aug 6, 2026
Overview
Processed 4 eligible non-draft PRs from the compact candidate set and nudged all 4. Branch refresh was requested on each PR; formatter runs were attempted locally but
make fmtfailed in this environment for every branch, so no formatter-only pushes were made.Critical Information
Nudged PRs
toolsettypo andallowed-repos: currentlegacy alias #50841 — Add fix codemods fortoolsettypo andallowed-repos: currentlegacy aliasRecommendations
Maintainters can review the fresh nudge comments for the next unblock action on each PR. PR #50856 was directed to resolve merge conflicts via
make merge-main; the other PRs were asked to address current review/check feedback and run thepr-finisherskill after branch refresh.github-actions commentedon Aug 6, 2026
Overview
Processed 5 candidate pull requests from the compact queue. No PRs were nudged because per-PR triage failed before actionable classification.
Critical Information
Skipped PRs
Recommendations
Investigate the PR processor/triage query path used for per-PR analysis; all candidates failed uniformly with
sub_agent_error.github-actions commentedon Aug 6, 2026
Nudged PRs
github-actions commentedon Aug 6, 2026
Overview
Processed 4 candidate PRs from the compact queue and posted 4 nudges. I could not run the documented
gh aw checksbackup check because the extension is not installed in this environment, andgh pr checksreturned a GraphQL access error, so no additional check-running skips were applied beyond the compact prefilter.Critical Information
Nudged PRs
Recommendations
Maintainers can investigate the nudged PRs directly. PRs #50928 and #50910 still show unresolved review threads in the fetched review-thread snapshot and were nudged with direct thread links.
github-actions commentedon Aug 7, 2026
This issue is being closed as outdated. A newer issue has been created: #50950
View newer issue
This action was performed automatically by the
PR Sous Chefworkflow.