Repository navigation
fix: retain diagnostics for failed updates - #18
Merged
Merged
Conversation
3ru
force-pushed
the
fix/update-diagnostics
branch
from
October 4, 2026 08:32
71adac2 to
ad95db6
Compare
3ru
added this pull request to stack #19
October 4, 2026 09:16
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
1 participant
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.
Save logs and input changes when updates fail. Preserve command failures, handle incomplete diagnostics, and respect output backpressure. Fix report paths and propagate Git read errors in the update PR command.
Depends on #17. Validation: npm run validate; TypeScript integration gate; package dry run; reporting without installed dependencies.