[ci-scan-feedback] Fix push to existing feedback PR on scheduled runs#7620
Merged
kotlarmilos merged 2 commits intoJun 9, 2026
Merged
Conversation
The feedback workflow runs on a schedule, so there is no triggering pull request. push-to-pull-request-branch and update-pull-request defaulted to target: triggering, which fails with "requires pull request context" and cancels the remaining safe outputs, so the agent can never add commits to the existing [ci-scan-feedback] PR. Set target: "*" on both so they operate on the PR discovered in Step 6, and constrain push-to-pull-request-branch with title-prefix "[ci-scan-feedback] " so it can only push to the feedback PR. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the gh-aw safe-outputs configuration for the CI Failure Scanner - Feedback (machinelearning) agentic workflow so scheduled runs (which have no triggering PR context) can correctly push updates to an already-open [ci-scan-feedback] feedback PR.
Changes:
- Configure
push-to-pull-request-branchto usetarget: "*"and restrict pushes to PRs whose titles start with[ci-scan-feedback]. - Configure
update-pull-requestto usetarget: "*"so it can update the discovered feedback PR on scheduled runs. - Regenerate the compiled
.agent.lock.ymlwith the updated safe-outputs settings.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/ci-scan-feedback.agent.md | Updates safe-outputs configuration to support scheduled runs updating an existing feedback PR. |
| .github/workflows/ci-scan-feedback.agent.lock.yml | Regenerated compiled workflow reflecting the updated safe-outputs configuration. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 1
anicka-net
approved these changes
Jun 8, 2026
Set title: false so the update-pull-request safe-output can only append to the feedback PR body, not rename it. Reduces blast radius if the agent selects the wrong PR under target: "*". Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
/ba-g build analysis is taking too long (>1h) |
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.
Problem
The
CI Failure Scanner - Feedback (machinelearning)workflow runs on a dailyschedule, so there is no triggering pull request. Itspush-to-pull-request-branchandupdate-pull-requestsafe-outputs defaulted totarget: triggering, which fails at runtime withpush-to-pull-request-branch with target "triggering" requires pull request contextand cancels the remaining safe outputs.Step 6 of the prompt instructs the agent to push new edits onto the existing
[ci-scan-feedback]PR when one is open. That push can never succeed on a scheduled run. (This is the same defect being fixed in dotnet/runtime#129132.)Fix
target: "*"onpush-to-pull-request-branchandupdate-pull-requestso they operate on the PR the agent discovers in Step 6 rather than a (nonexistent) triggering PR. This mirrorsupdate-issue, which already usestarget: "*".push-to-pull-request-branchwithtitle-prefix: "[ci-scan-feedback] "so it can only push to the feedback PR..lock.ymlregenerated withgh aw compile(v0.71.5, matching the committed compiler version).