Add noop instructions to repo-assist and regression-pr-shepherd workflows#19567
Open
Add noop instructions to repo-assist and regression-pr-shepherd workflows#19567
Conversation
…lows Reinforce noop requirement at key decision points: - repo-assist: Command Mode exit path and Task FINAL fallthrough - regression-pr-shepherd: When no eligible PRs exist Fixes #17258 workflow failure (no safe outputs produced) Agent-Logs-Url: https://github.com/dotnet/fsharp/sessions/ac165649-72fa-4613-bd06-fcdc9604f176 Co-authored-by: T-Gro <46543583+T-Gro@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Repo Assist failed workflow issue
Add noop instructions to repo-assist and regression-pr-shepherd workflows
Apr 10, 2026
T-Gro
approved these changes
Apr 10, 2026
Contributor
✅ No release notes required |
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.
Repo Assist run #24221061841 completed successfully but produced zero safe outputs, which the infrastructure treats as a failure. The agent should have called
noopto explicitly signal no action was needed.The existing
noopinstruction was buried in the "Safe Output Discipline" section at the bottom of the file — not at the actual decision points where the agent concludes "nothing to do."Changes
repo-assist.md: Addednoopreminders at two decision points:regression-pr-shepherd.md: Addednoopinstruction when no eligible PRs exist after filtering (same gap)gh aw compile