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.
Honor
gh aw fixdry-run for dispatcher agent and skill refresh #47269New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Honor
gh aw fixdry-run for dispatcher agent and skill refresh #47269Changes from all commits
81d43dbabc811bf1dcb2aa12ae9d4c8f2993694b7dee5d629File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/codebase-design] The
write boolparameter onwriteGeneratedRepositoryInstructionFileis redundant — the function already guards!writeat line 168 and errors out. Since callers already perform the dry-run check before reaching this helper, the parameter creates misleading surface area.💡 Suggestion
Remove the
writeparameter and the internal guard. Callers already checkif !write { ... return }before this call site, so the guard is unreachable in practice. This also lets you wrap theWriteFileerror properly:@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
write boolparameter is dead at every production call site — both callers guard withif !write { return nil }before invoking this function, sowriteis alwaystruehere. The internal-error branch is unreachable from real code and only fires in the unit test that calls the helper directly.💡 Suggested fix
Remove the
writeparameter and the dead guard entirely. The invariant is already enforced by callers:If the intent is to protect against accidental misuse, enforce it via a panic (programming error) rather than a returned error that the unit test then has to special-case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
os.WriteFileerror is returned without context, making failures impossible to diagnose. Every other error in this file is wrapped; this barereturn errloses which file and operation failed.💡 Suggested fix
Without this, callers that log the error see only
"permission denied"or"no space left on device"with no indication of the affected path.Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.