Fix TUI corruption on git clone/sync failures and display error details #11
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.
When git operations fail in TUI mode, error messages were printed directly to stdout, breaking the terminal layout and corrupting progress displays. This PR fixes the corruption issue while ensuring users are informed about failures.
Changes
internal/sync/sync.go: Guard all
fmt.Printfcalls withs.opts.VerbosecheckssyncSingleRepo(2 locations)syncWorkerandsyncSingleRepo(4 locations)internal/tui/screens/sync_progress.go: Add error tracking and display
failedReposmap to capture error messages during syncIn TUI mode, the syncer runs with
Verbose: falseand Git in quiet mode, so all progress is communicated via callbacks (s.reportProgress). The unguarded print statements bypassed that mechanism, breaking the layout. Errors are now captured and displayed in a dedicated section after sync completes.Example
Code changes:
UI changes:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.